Communications bladed panel systems

ABSTRACT

A fiber panel system includes a chassis and at least blades configured to mount to the chassis. Each blade is moveable relative to the chassis between a retracted (closed) position and at least one extended position. Cable slack is managed at the front and/or rear of each chassis to facilitate movement of the blades without pulling or bending the cables beyond a maximum bend limit. Each blade may be locked into one or more positions relative to the chassis.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of application Ser. No. 15/043,897,filed Feb. 15, 2016, which is a continuation of application Ser. No.14/574,596, filed Dec. 18, 2014, now U.S. Pat. No. 9,265,172, which is acontinuation of application Ser. No. 13/025,750, filed Feb. 11, 2011,now U.S. Pat. No. 8,923,013, which application claims the benefit ofprovisional application Ser. No. 61/303,948, filed Feb. 12, 2010, titled“Bladed Communications System;” U.S. Provisional Application No.61/413,844, filed Nov. 15, 2010, titled “Communications Bladed PanelSystems;” and U.S. Provisional Application No. 61/439,693, filed Feb. 4,2011, titled “Communications Bladed Panel Systems,” which applicationsare incorporated herein by reference in their entirety.

BACKGROUND

In communications infrastructure installations, a variety ofcommunications devices can be used for switching and connectingcommunications signal transmission paths in a communications network.Some such communications devices are installed in one or more equipmentracks to permit organized, high-density installations to be achieved inlimited space available for equipment.

Installing a large number of connections in an equipment rack isefficient with respect to floor space, but places a premium on theability to manage and maintain the communications cables leading to andaway from these equipment racks. Further, due to the increasing demandfor communications system capacity, it is desirable to increase thedensity of connections within a given space that can be achieved.

Network management systems (NMS) are typically aware of logicalcommunication links that exist in a communications network, buttypically do not have information about the specific physical layermedia (e.g., the communications devices, cables, couplers, etc.) thatare used to implement the logical communication links. Indeed, NMSsystems typically do not have the ability to display or otherwiseprovide information about how logical communication links areimplemented at the physical layer level.

SUMMARY

The present disclosure relates to communications panels which provide ahigher density of connections within a given floor space, provideimproved cable management structures, and provide physical layermanagement capabilities. One or more communications devices forproviding such connections can be bundled into compact operationalunits, known as blades.

One aspect of the present disclosure relates to a communications panelsystem including one or more blades mounted to a chassis.

In some implementations, the blades are configured to move separatelyrelative to the chassis.

In some implementations, the blades are each configured to providephysical layer information (PLI) functionality and physical layermanagement (PLM) functionality.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute apart of the description, illustrate several aspects of the presentdisclosure. A brief description of the drawings is as follows:

FIG. 1 is a diagram of a portion of an example communications and datamanagement system in accordance with aspects of the present disclosure;

FIG. 2 is a block diagram of one implementation of a communicationsmanagement system that includes PLI functionality as well as PLMfunctionality in accordance with aspects of the present disclosure;

FIG. 3 is a block diagram of one high-level example of a port and mediareading interface that are suitable for use in the management system ofFIG. 2 in accordance with aspects of the present disclosure;

FIGS. 4-24 provide an example connector assembly implemented as a bladedpanel system configured to support PLI functionality as well as PLMfunctionality in accordance with aspects of the present disclosure; and

FIGS. 25-44 provide another example connector assembly implemented as abladed panel system configured to support PLI functionality as well asPLM functionality in accordance with aspects of the present disclosure;

FIGS. 45-49 illustrate one example chassis of a bladed panel systemsuitable for receiving one or more blades in accordance with aspects ofthe present disclosure;

FIGS. 50-51 illustrate another example chassis of a bladed panel systemsuitable for receiving one or more blades in accordance with aspects ofthe present disclosure;

FIGS. 52-53 illustrate another example chassis of a bladed panel systemsuitable for receiving one or more blades in accordance with aspects ofthe present disclosure;

FIGS. 54-56 illustrate an example blade suitable for receipt in any ofthe chasses shown in FIGS. 25-51 in accordance with aspects of thepresent disclosure;

FIGS. 57-62 illustrate one example blade including a coupler arrangementthat connects incoming media segments terminated at LC-type connectorsto outgoing media segments terminated at LC-type connectors;

FIGS. 63-66 illustrate another example blade including a couplerarrangement that connects incoming media segments terminated at MPO-typeconnectors to outgoing media segments terminated at MPO-type connectors;

FIGS. 67-71 illustrate one example blade including a coupler arrangementthat connects incoming media segments terminated at MPO-type connectorsto outgoing media segments terminated at LC-type connectors;

FIGS. 72-74 illustrate one example labeling assembly suitable for usewith any of the blades disclosed herein;

FIGS. 75 and 76 illustrate one example bladed panel system in which aplurality of blades is mounted within an example chassis with a topblade shown in a closed position relative to the chassis, a middle bladeshown in a first extended position relative to the chassis, and a bottomblade shown in a second extended position relative to the chassis;

FIGS. 77-79 show rear perspective views of a bladed panel systemincluding management structures at the rear of the chassis and the rearof the blades;

FIGS. 80-90 illustrate an example bladed panel system in which at leastone chassis and at least one bracket are mounted to a frame tofacilitate management of the outgoing media segments as blades are movedrelative to the chassis;

FIG. 91 is a front perspective view of an example chassis and backplanewith a top of the chassis removed so that the interior of the chassisand a blade positioned in the chassis are visible;

FIGS. 92-94 are enlarged views of the interior of the chassis shown inFIG. 91 to illustrate an example latching arrangement by which a blademay be latched into the closed position relative to the chassis;

FIGS. 95-98 illustrate an example latching arrangement by which a blademay be latched in at least the first extended position relative to thechassis;

FIGS. 99-113 show another example latching arrangement that isconfigured to secure blade in at least the first extended positionrelative to chassis;

FIGS. 114-117 show another example latching arrangement that isconfigured to secure a blade in at least the first extended positionrelative to a chassis;

FIGS. 118-127 show another example bladed chassis system including anexample chassis that is configured to receive one or more blades havinganother example latching arrangement that is configured to secure eachblade in at least the first extended position relative to a chassis;

FIG. 128 is a perspective view of an example smart blade including acircuit board arrangement, a connection system, a blade processor, and asmart coupler arrangement in accordance with aspects of the disclosure;

FIG. 129A is a cross-sectional view of an example smart couplerincluding a media reading interface that is contacting a storage deviceof an LC-type fiber optic connector received at a respective port of thesmart coupler in accordance with aspects of the disclosure;

FIG. 129B is a perspective view of an example smart coupler includingmedia reading interfaces that are configured to contact storage devicesof MPO-type fiber optic connectors received at the port of the smartcoupler in accordance with aspects of the disclosure;

FIG. 130A is a perspective view of the example LC-type fiber opticconnector of FIG. 129A;

FIG. 130B is an exploded, perspective view of an example MPO-type fiberoptic connector that is suitable for receipt at a port of the smartcoupler shown in FIG. 129B;

FIGS. 131-135 show an example connection system that enables a smartblade to remain connected to a chassis backplane when the smart blademoves relative to the chassis in accordance with aspects of thedisclosure;

FIGS. 136-142 show another example connection system that enables asmart blade to remain connected to a chassis backplane when the smartblade moves relative to the chassis in accordance with aspects of thedisclosure; and

FIGS. 143-150 illustrate one example bladed panel system including a“passive” chassis and a plurality of “passive” blades in accordance withaspects of the disclosure.

DETAILED DESCRIPTION

The present disclosure is directed to bladed distribution panel systemsfor use in communications networks. The bladed distribution panelsystems include one or more bladed distribution modules that areconfigured to connect together two or more cables. Certain types ofbladed distribution modules include one or more first cable ports atwhich terminated ends of first cables (e.g., patch cables) can beplugged and one or more second cable ports at which terminated ends ofsecond cables (e.g., distribution cables) can be plugged. Opposite endsof the first cables can connect together ports of two or more bladeddistribution modules. Opposite ends of the second cables can connect thebladed distribution modules to a larger communications network as willbe described in more detail herein. Communications signals pass throughthe bladed distribution modules between the first cables and the secondcables.

In addition, PLI (physical layer information) cables also may be routedto the bladed distribution modules. In accordance with some aspects, thePLI cables may provide power (e.g., electrical power) to the bladeddistribution modules. In accordance with other aspects, the PLI cablesmay carry additional data signals between the bladed distributionmodules and a data network as will be described in more detail herein.In certain implementations, the data network is different from thecommunications network to which the second cables connect.

As the term is used herein, a “cable” refers to a physical medium thatis capable of carrying one or more data signals along its length.Non-limiting examples of suitable cables include fiber cables,electrical cables, and hybrid cables. For example, a fiber optic cableincludes one or more optical fibers that are configured to carry opticalsignals along their length. The fibers in a fiber optic cable may bebuffered and/or jacketed (e.g., individually or as a group). Certaintypes of fiber optic cables may be terminated with one or moreconnectors (e.g., SC, LC, FC, LX.5, or MPO connectors).

An electrical cable includes one or more conductors (e.g., wires) thatare configured to carry electrical signals along their length. Theconductors in an electrical cable may be insulated (e.g., individuallyor as a group). Non-limiting examples of electrical cables includeCAT-5, 6, and 7 twisted-pair cables, DS1 line, and DS3 line. Certaintypes of electrical cables may be terminated with one or more connectorsor connector assemblies (e.g., RJ jacks and plugs, DSX jacks and plugs,BNC connectors, F connectors, punch-down terminations, or bantam jacksand plugs). A hybrid cable includes a combination of one or more wiresand one or more optical fibers that may be insulated/jacketed.

Reference will now be made in detail to exemplary aspects of the presentdisclosure that are illustrated in the accompanying drawings. Whereverpossible, the same reference numbers will be used throughout thedrawings to refer to the same or like parts.

FIG. 1 is a diagram of a portion of an example communications and datamanagement system 100. The example system 100 shown in FIG. 1 includes apart of a communications network 101 along which communications signalsS1 pass. In one example implementation, the network 101 can include anInternet Protocol network. In other implementations, however, thecommunications network 101 may include other types of networks.

The communications network 101 includes connected network components(e.g., connector assemblies, inter-networking devices, internet workingdevices, servers, outlets, and end user equipment (e.g., computers)). Inone example implementation, communications signals S1 pass from acomputer, to a wall outlet, to a port of communication panel, to a firstport of an inter-networking device, out another port of theinter-networking device, to a port of the same or another communicationspanel, to a rack mounted server. In other implementations, thecommunications signals S1 may follow other paths within thecommunications network 101.

The portion of the communications network 101 shown in FIG. 1 includesfirst and second connector assemblies 130, 130′ at which communicationssignals S1 pass from one portion of the communications network 101 toanother portion of the communications network 101. Non-limiting examplesof connector assemblies 130, 130′ include, for example, rack-mountedconnector assemblies (e.g., patch panels, distribution units, and mediaconverters for fiber and copper physical communication media),wall-mounted connector assemblies (e.g., boxes, jacks, outlets, andmedia converters for fiber and copper physical communication media), andinter-networking devices (e.g., switches, routers, hubs, repeaters,gateways, and access points).

In the example shown, the first connector assembly 130 defines at leastone port 132 configured to communicatively couple at least a first mediasegment (e.g., cable) 105 to at least a second media segment (e.g.,cable) 115 to enable the communication signals S1 to pass between themedia segments 105, 115. The at least one port 132 of the firstconnector assembly 130 may be directly connected to a port 132′ of thesecond connector assembly 130′. As the term is used herein, the port 132is directly connected to the port 132′ when the communications signalsS1 pass between the two ports 132, 132′ without passing through anintermediate port. For example, plugging a first terminated end of apatch cable into the port 132 and a second terminated end of the patchcable into the port 132′ directly connects the ports 132, 132′.

The port 132 of the first connector assembly 130 also may be indirectlyconnected to the port 132′ of the second connector assembly 130′. As theterm is used herein, the port 132 is indirectly connected to the port132′ when the communications signals S1 pass through an intermediateport when traveling between the ports 132, 132′. For example, in oneimplementation, the communications signals S1 may be routed over onemedia segment from the port 132 at the first connector assembly 130, toa port of a third connector assembly at which the media segment iscoupled, to another media segment that is routed from the port of thethird connector assembly to the port 132′ of the second connectorassembly 130′.

Non-limiting examples of media segments include optical cables,electrical cables, and hybrid cables. The media segments may beterminated with electrical plugs, electrical jacks, fiber opticconnectors, fiber optic adapters, media converters, or other terminationcomponents. In the example shown, each media segment 105, 115 isterminated at a plug or connector 110, 120, respectively, which isconfigured to communicatively connect the media segments 105, 115. Forexample, in one implementation, the port 132 of the connector assembly130 can be configured to align ferrules of two fiber optic connectors110, 120. In another implementation, the port 132 of the connectorassembly 130 can be configured to electrically connect an electricalplug with an electrical socket (e.g., a jack). In yet anotherimplementation, the port 132 can include a media converter configured toconnect an optical fiber to an electrical conductor.

In accordance with some aspects, the connector assembly 130 does notactively manage (e.g., is passive with respect to) the communicationssignals S1 passing through port 132. For example, in someimplementations, the connector assembly 130 does not modify thecommunications signal S1 carried over the media segments 105, 115.Further, in some implementations, the connector assembly 130 does notread, store, or analyze the communications signal S1 carried over themedia segments 105, 115.

In accordance with aspects of the disclosure, the communications anddata management system 100 also provides physical layer information(PLI) functionality as well as physical layer management (PLM)functionality. As the term is used herein, “PLI functionality” refers tothe ability of a physical component or system to identify or otherwiseassociate physical layer information with some or all of the physicalcomponents used to implement the physical layer of the system. As theterm is used herein, “PLM functionality” refers to the ability of acomponent or system to manipulate or to enable others to manipulate thephysical components used to implement the physical layer of the system(e.g., to track what is connected to each component, to traceconnections that are made using the components, or to provide visualindications to a user at a selected component).

As the term is used herein, “physical layer information” refers toinformation about the identity, attributes, and/or status of thephysical components used to implement the physical layer of thecommunications system 100. In accordance with some aspects, physicallayer information of the communications system 100 can include mediainformation, device information, and location information.

As the term is used herein, “media information” refers to physical layerinformation pertaining to cables, plugs, connectors, and other suchphysical media. In accordance with some aspects, the media informationis stored on or in the physical media, themselves. In accordance withother aspects, the media information can be stored at one or more datarepositories for the communications system, either alternatively or inaddition to the media, themselves.

Non-limiting examples of media information include a part number, aserial number, a plug or other connector type, a conductor or fibertype, a cable or fiber length, cable polarity, a cable or fiberpass-through capacity, a date of manufacture, a manufacturing lotnumber, information about one or more visual attributes of physicalcommunication media (e.g., information about the color or shape of thephysical communication media or an image of the physical communicationmedia), and an insertion count (i.e., a record of the number of timesthe media segment has been connected to another media segment or networkcomponent). Media information also can include testing or media qualityor performance information. The testing or media quality or performanceinformation, for example, can be the results of testing that isperformed when a particular segment of media is manufactured.

As the term is used herein, “device information” refers to physicallayer information pertaining to the communications panels,inter-networking devices, media converters, computers, servers, walloutlets, and other physical communications devices to which the mediasegments attach. In accordance with some aspects, the device informationis stored on or in the devices, themselves. In accordance with otheraspects, the device information can be stored at one or more datarepositories for the communications system, either alternatively or inaddition to the devices, themselves. In accordance with still otheraspects, the device information can be stored in the media segmentsattached thereto. Non-limiting examples of device information include adevice identifier, a device type, port priority data (that associates apriority level with each port), and port updates (described in moredetail herein).

As the term is used herein, “location information” refers to physicallayer information pertaining to a physical layout of a building orbuildings in which the network 101 is deployed. Location informationalso can include information indicating where each communicationsdevice, media segment, network component, or other component isphysically located within the building. In accordance with some aspects,the location information of each system component is stored on or in therespective component. In accordance with other aspects, the locationinformation can be stored at one or more data repositories for thecommunications system, either alternatively or in addition to the systemcomponents, themselves.

In accordance with some aspects, one or more of the components of thecommunications network 101 are configured to store physical layerinformation pertaining to the component as will be disclosed in moredetail herein. In FIG. 1, the connectors 110, 120, the media segments105, 115, and/or the connector assemblies 130, 130′ may store physicallayer information. For example, in FIG. 1, each connector 110, 120 maystore information pertaining to itself (e.g., type of connector, data ofmanufacture, etc.) and/or to the respective media segment 105, 115(e.g., type of media, test results, etc.).

In another example implementation, the media segments 105, 115 orconnectors 110, 120 may store media information that includes a count ofthe number of times that the media segment (or connector) has beeninserted into port 132. In such an example, the count stored in or onthe media segment is updated each time the segment (or plug orconnector) is inserted into port 132. This insertion count value can beused, for example, for warranty purposes (e.g., to determine if theconnector has been inserted more than the number of times specified inthe warranty) or for security purposes (e.g., to detect unauthorizedinsertions of the physical communication media).

One or more of the components of the communications network 101 can readthe physical layer information from one or more media segments retainedthereat. In certain implementations, one or more network componentsincludes a media reading interface that is configured to read physicallayer information stored on or in the media segments or connectorsattached thereto. For example, in one implementation, the connectorassembly 130 includes a media reading interface 134 that can read mediainformation stored on the media cables 105, 115 retained within the port132. In another implementation, the media reading interface 134 can readmedia information stored on the connectors or plugs 110, 120 terminatingthe cables 105, 115, respectively.

In accordance with some aspects of the disclosure, the physical layerinformation read by a network component may be processed or stored atthe component. For example, in certain implementations, the firstconnector assembly 130 shown in FIG. 1 is configured to read physicallayer information stored on the connectors 110, 120 and/or on the mediasegments 105, 115 using media reading interface 134. Accordingly, inFIG. 1, the first connector assembly 130 may store not only physicallayer information about itself (e.g., the total number of availableports at that assembly 130, the number of ports currently in use, etc.),but also physical layer information about the connectors 110, 120inserted at the ports and/or about the media segments 105, 115 attachedto the connectors 110, 120.

The physical layer information obtained by the media reading interfacemay be communicated (see PLI signals S2) over the network 101 forprocessing and/or storage. In accordance with some aspects, thecommunications network 101 includes a data network (e.g., see network218 of FIG. 2) along which the physical layer information iscommunicated. At least some of the media segments and other componentsof the data network may be separate from those of the communicationsnetwork 101 to which such physical layer information pertains. Forexample, in some implementations, the first connector assembly 130 mayinclude a plurality of “normal” ports (e.g., fiber optic adapter ports)at which connectorized media segments (e.g., optical fibers) are coupledtogether to create a path for communications signals S1. The firstconnector assembly 130 also may include one or more PLI ports 136 atwhich the physical layer information (see PLI signals S2) are passed tocomponents of the data network (e.g., to one or more aggregation points150 and/or to one or more computer systems 160).

In other implementations, however, the physical layer information may becommunicated over the communications network 101 just like any othersignal, while at the same time not affecting the communication signalsS1 that pass through the connector assembly 130 on the normal ports 132.Indeed, in some implementations, the physical layer information may becommunicated as one or more of the communication signals S1 that passthrough the normal ports 132 of the connector assemblies 130, 130′. Forexample, in one implementation, a media segment may be routed betweenthe PLI port 136 and one of the “normal” ports 132. In anotherimplementation, the media segment may be routed between the PLI port 136and a “normal” port of another connector assembly. In suchimplementations, the physical layer information may be passed along thecommunications network 101 to other components of the communicationsnetwork 101 (e.g., to another connector assembly, to one or moreaggregation points 150 and/or to one or more computer systems 160). Byusing the network 101 to communicate physical layer informationpertaining to it, an entirely separate data network need not be providedand maintained in order to communicate such physical layer information.

For example, in the implementation shown in FIG. 1, each connectorassembly 130 includes at least one PLI port 136 that is separate fromthe “normal” ports 132 of the connector assembly 130. Physical layerinformation is communicated between the connector assembly 130 and thecommunications network 101 through the PLI port 136. Components of thecommunications network 101 may be connected to one or more aggregationdevices 150 and/or to one or more computing systems 160. In the exampleshown in FIG. 1, the connector assembly 130 is connected to arepresentative aggregation device 150, a representative computing system160, and to other components of the network 101 (see looped arrows) viathe PLI port 136.

In some implementations, some types of physical layer informationpertaining to media segments can be obtained by the connector assembly130 from a user at the connector assembly 130 via a user interface(e.g., a keypad, a scanner, a touch screen, buttons, etc.). For example,physical layer information pertaining to media that is not configured tostore such information can be entered manually into the connectorassembly 130 by the user. In certain implementations, the connectorassembly 130 can provide the physical layer information obtained fromthe user to other devices or systems that are coupled to thecommunications network 101 and/or a separate data network.

In other implementations, some or all physical layer information can beobtained by the connector assembly 130 from other devices or systemsthat are coupled to the communications network 101 and/or a separatedata network. For example, physical layer information pertaining tomedia that is not configured to store such information can be enteredmanually into another device or system (e.g., at the connector assembly130, at the computer 160, or at the aggregation point 150) that iscoupled to the network 101 and/or a separate data network.

In some implementations, some types of non-physical layer information(e.g., network information) also can be obtained by one networkcomponent (e.g., a connector assembly 130, an aggregation point 150, ora computer 160) from other devices or systems that are coupled to thecommunications network 101 and/or a separate data network. For example,the connector assembly 130 may pull non-physical layer information fromone or more components of the network 101. In other implementations, thenon-physical layer information can be obtained by the connector assembly130 from a user at the connector assembly 130.

In some implementations, the connector assembly 130 is configured tomodify (e.g., add, delete, and/or change) the physical layer informationstored in or on the segment of physical communication media 105, 115(i.e., or the associated connectors 110, 120). For example, in someimplementations, the media information stored in or on the segment ofphysical communication media 105, 115 can be updated to include theresults of testing that is performed when a segment of physical media isinstalled or otherwise checked. In other implementations, such testinginformation is supplied to the aggregation point 150 for storage and/orprocessing. The modification of the physical layer information does notaffect the communications signals S1 passing through the connectorassembly 130.

FIG. 2 is a block diagram of one example implementation of acommunications management system 200 that includes PLI functionality aswell as PLM functionality.

The management system 200 comprises a plurality of connector assemblies202. The management system 200 includes one or more connector assemblies202 connected to an IP network 218. The connector assemblies 202 shownin FIG. 2 illustrate various example implementations of the connectorassemblies 130, 30′ of FIG. 1.

Each connector assembly 202 includes one or more ports 204, each ofwhich is used to connect two or more segments of physical communicationmedia to one another (e.g., to implement a portion of a logicalcommunication link for communication signals S1 of FIG. 1). At leastsome of the connector assemblies 202 are designed for use with segmentsof physical communication media that have physical layer informationstored in or on them. The physical layer information is stored in or onthe segment of physical communication media in a manner that enables thestored information, when the segment is attached to a port 204, to beread by a programmable processor 206 associated with the connectorassembly 202.

Each programmable processor 206 is configured to execute software orfirmware that causes the programmable processor 206 to carry out variousfunctions described below. Each programmable processor 206 also includessuitable memory (not shown) that is coupled to the programmableprocessor 206 for storing program instructions and data. In general, theprogrammable processor 206 determines if a physical communication mediasegment is attached to a port 204 with which that processor 206 isassociated and, if one is, to read the identifier and attributeinformation stored in or on the attached physical communication mediasegment (if the segment includes such information stored therein orthereon) using the associated media reading interface 208.

In some implementations, each of the ports 204 of the connectorassemblies 202 comprises a respective media reading interface 208 viawhich the respective programmable processor 206 is able to determine ifa physical communication media segment is attached to that port 204 and,if one is, to read the physical layer information stored in or on theattached segment (if such media information is stored therein orthereon). In other implementations, a single media reading interface 208may correspond to two or more ports 204. The programmable processor 206associated with each connector assembly 202 is communicatively coupledto each of the media reading interfaces 208 using a suitable bus orother interconnect (not shown).

In FIG. 2, four example types of connector assembly configurations 210,212, 214, and 215 are shown. In the first connector assemblyconfiguration 210 shown in FIG. 2, each connector assembly 202 includesits own respective programmable processor 206 and its own respectivenetwork interface 216 that is used to communicatively couple thatconnector assembly 202 to an Internet Protocol (IP) network 218. In someimplementations, the ports 204 of the connector assemblies 202 alsoconnect to the IP network 218. In other implementations, however, onlythe network interfaces 216 couple to the IP network 218.

In the second type of connector assembly configuration 212, a group ofconnector assemblies 202 are physically located near each other (e.g.,in a rack, rack system, or equipment closet). Each of the connectorassemblies 202 in the group includes its own respective programmableprocessor 206. However, in the second connector assembly configuration212, some of the connector assemblies 202 (referred to here as“interfaced connector assemblies”) include their own respective networkinterfaces 216 while some of the connector assemblies 202 (referred tohere as “non-interfaced connector assemblies”) do not. Thenon-interfaced connector assemblies 202 are communicatively coupled toone or more of the interfaced connector assemblies 202 in the group vialocal connections. In this way, the non-interfaced connector assemblies202 are communicatively coupled to the IP network 218 via the networkinterface 216 included in one or more of the interfaced connectorassemblies 202 in the group. In the second type of connector assemblyconfiguration 212, the total number of network interfaces 216 used tocouple the connector assemblies 202 to the IP network 218 can bereduced. Moreover, in the particular implementation shown in FIG. 2, thenon-interfaced connector assemblies 202 are connected to the interfacedconnector assembly 202 using a daisy chain topology (though othertopologies can be used in other implementations and embodiments).

In the third type of connector assembly configuration 214, a group ofconnector assemblies 202 are physically located near each other (e.g.,within a rack, rack system, or equipment closet). Some of the connectorassemblies 202 in the group (also referred to here as “master” connectorassemblies 202) include both their own programmable processors 206 andnetwork interfaces 216, while some of the connector assemblies 202 (alsoreferred to here as “slave” connector assemblies 202) do not includetheir own programmable processors 206 or network interfaces 216. Each ofthe slave connector assemblies 202 is communicatively coupled to one ormore of the master connector assemblies 202 in the group via one or morelocal connections. The programmable processor 206 in each of the masterconnector assemblies 202 is able to carry out the PLM functions for boththe master connector assembly 202 of which it is a part and any slaveconnector assemblies 202 to which the master connector assembly 202 isconnected via the local connections. As a result, the cost associatedwith the slave connector assemblies 202 can be reduced. In theparticular implementation shown in FIG. 2, the slave connectorassemblies 202 are connected to a master connector assembly 202 in astar topology (though other topologies can be used in otherimplementations and embodiments).

In the fourth type of connector assembly configuration 215, a group ofconnector assemblies (e.g., distribution modules) 202 are housed withina common chassis or other enclosure. Each of the connector assemblies202 in the configuration 215 includes their own programmable processors206. In the context of this configuration 215, the programmableprocessors 206 in the connector assemblies 202 are “slave” processors206. Each of the slave programmable processors 206 in the group iscommunicatively coupled to a common “master” programmable processor 217(e.g., over a backplane included in the chassis or enclosure). Themaster programmable processor 217 is coupled to a network interface 216that is used to communicatively couple the master programmable processor217 to the IP network 218.

In the fourth configuration 215, each slave programmable processor 206is configured to manage the media reading interfaces 208 to determine ifphysical communication media segments are attached to the port 204 andto read the physical layer information stored in or on the attachedphysical communication media segments (if the attached segments havesuch information stored therein or thereon). The physical layerinformation is communicated from the slave programmable processor 206 ineach of the connector assemblies 202 in the chassis to the masterprocessor 217. The master processor 217 is configured to handle theprocessing associated with communicating the physical layer informationread from by the slave processors 206 to devices that are coupled to theIP network 218.

In accordance with some aspects, the communications management system200 includes functionality that enables the physical layer informationcaptured by the connector assemblies 202 to be used by application-layerfunctionality outside of the traditional physical-layer managementapplication domain. That is, the physical layer information is notretained in a PLM “island” used only for PLM purposes but is insteadmade available to other applications. For example, in the particularimplementation shown in FIG. 2, the management system 200 includes anaggregation point 220 that is communicatively coupled to the connectorassemblies 202 via the IP network 218.

The aggregation point 220 includes functionality that obtains physicallayer information from the connector assemblies 202 (and other devices)and stores the physical layer information in a data store. Theaggregation point 220 can be used to receive physical layer informationfrom various types of connector assemblies 202 that have functionalityfor automatically reading information stored in or on the segment ofphysical communication media. Also, the aggregation point 220 andaggregation functionality 224 can be used to receive physical layerinformation from other types of devices that have functionality forautomatically reading information stored in or on the segment ofphysical communication media. Examples of such devices include end-userdevices—such as computers, peripherals (e.g., printers, copiers, storagedevices, and scanners), and IP telephones—that include functionality forautomatically reading information stored in or on the segment ofphysical communication media.

The aggregation point 220 also can be used to obtain other types ofphysical layer information. For example, in this implementation, theaggregation point 220 also obtains information about physicalcommunication media segments that is not otherwise automaticallycommunicated to an aggregation point 220. This information can beprovided to the aggregation point 220, for example, by manually enteringsuch information into a file (e.g., a spreadsheet) and then uploadingthe file to the aggregation point 220 (e.g., using a web browser) inconnection with the initial installation of each of the various items.Such information can also, for example, be directly entered using a userinterface provided by the aggregation point 220 (e.g., using a webbrowser).

The aggregation point 220 also includes functionality that provides aninterface for external devices or entities to access the physical layerinformation maintained by the aggregation point 220. This access caninclude retrieving information from the aggregation point 220 as well assupplying information to the aggregation point 220. In thisimplementation, the aggregation point 220 is implemented as “middleware”that is able to provide such external devices and entities withtransparent and convenient access to the PLI maintained by the accesspoint 220. Because the aggregation point 220 aggregates PLI from therelevant devices on the IP network 218 and provides external devices andentities with access to such PLI, the external devices and entities donot need to individually interact with all of the devices in the IPnetwork 218 that provide PLI, nor do such devices need to have thecapacity to respond to requests from such external devices and entities.

For example, as shown in FIG. 2, a network management system (NMS) 230includes PLI functionality 232 that is configured to retrieve physicallayer information from the aggregation point 220 and provide it to theother parts of the NMS 230 for use thereby. The NMS 230 uses theretrieved physical layer information to perform one or more networkmanagement functions. In certain implementations, the NMS 230communicates with the aggregation point 220 over the IP network 218. Inother implementations, the NMS 230 may be directly connected to theaggregation point 220.

As shown in FIG. 2, an application 234 executing on a computer 236 alsocan use the API implemented by the aggregation point 220 to access thePLI information maintained by the aggregation point 220 (e.g., toretrieve such information from the aggregation point 220 and/or tosupply such information to the aggregation point 220). The computer 236is coupled to the IP network 218 and accesses the aggregation point 220over the IP network 218.

In the example shown in FIG. 2, one or more inter-networking devices 238used to implement the IP network 218 include physical layer information(PLI) functionality 240. The PLI functionality 240 of theinter-networking device 238 is configured to retrieve physical layerinformation from the aggregation point 220 and use the retrievedphysical layer information to perform one or more inter-networkingfunctions. Examples of inter-networking functions include Layer 1, Layer2, and Layer 3 (of the OSI model) inter-networking functions such as therouting, switching, repeating, bridging, and grooming of communicationtraffic that is received at the inter-networking device.

The aggregation point 220 can be implemented on a standalone networknode (e.g., a standalone computer running appropriate software) or canbe integrated along with other network functionality (e.g., integratedwith an element management system or network management system or othernetwork server or network element). Moreover, the functionality of theaggregation point 220 can be distribute across many nodes and devices inthe network and/or implemented, for example, in a hierarchical manner(e.g., with many levels of aggregation points). The IP network 218 caninclude one or more local area networks and/or wide area networks (e.g.,the Internet). As a result, the aggregation point 220, NMS 230, andcomputer 236 need not be located at the same site as each other or atthe same site as the connector assemblies 202 or the inter-networkingdevices 238.

Also, power can be supplied to the connector assemblies 202 usingconventional “Power over Ethernet” techniques specified in the IEEE802.3af standard, which is hereby incorporated herein by reference. Insuch an implementation, a power hub 242 or other power supplying device(located near or incorporated into an inter-networking device that iscoupled to each connector assembly 202) injects DC power onto one ormore power cables (e.g., a power wire included in a copper twisted-paircable) used to connect each connector assembly 202 to the IP network218.

FIG. 3 is a schematic diagram of one example connection system 1800including a connector assembly 1810 configured to collect physical layerinformation from at least one segment of physical communications media.The example connector assembly 1810 of FIG. 3 is configured to connectsegments of optical physical communications media in a physical layermanagement system. The connector assembly 1810 includes a fiber opticadapter defining at least one connection opening 1811 having a firstport end 1812 and a second port end 1814. A sleeve (e.g., a splitsleeve) 1803 is arranged within the connection opening 1811 of theadapter 1810 between the first and second port ends 1812, 1814. Eachport end 1812, 1814 is configured to receive a connector arrangement aswill be described in more detail herein.

A first example segment of optical physical communication media includesa first optical fiber 1822 terminated by a first connector arrangement1820. A second example segment of optical physical communication mediaincludes a second optical fiber 1832 terminated by a second connectorarrangement 1830. The first connector arrangement 1820 is plugged intothe first port end 1812 and the second connector arrangement 1830 isplugged into the second port end 1814. Each fiber connector arrangement1820, 1830 includes a ferrule 1824, 1834 through which optical signalsfrom the optical fiber 1822, 1832, respectively, pass.

The ferrules 1824, 1834 of the connector arrangements 1820, 1830 arealigned by the sleeve 1803 when the connector arrangements 1820, 1830are inserted into the connection opening 1811 of the adapter 1810.Aligning the ferrules 1824, 1834 provides optical coupling between theoptical fibers 1822, 1832. In some implementations, each segment ofoptical physical communication media (e.g., each optical fiber 1822,1832) carries communication signals (e.g., communications signals S1 ofFIG. 1). The aligned ferrules 1824, 1834 of the connector arrangements1820, 1830 create an optical path along which the communication signals(e.g., signals S1 of FIG. 1) may be carried.

In some implementations, the first connector arrangement 1820 mayinclude a storage device 1825 that is configured to store physical layerinformation (e.g., an identifier and/or attribute information)pertaining to the segment of physical communications media (e.g., thefirst connector arrangement 1820 and/or the fiber optic cable 1822terminated thereby). In some implementations, the connector arrangement1830 also includes a storage device 1835 that is configured to storeinformation (e.g., an identifier and/or attribute information)pertaining to the second connector arrangement 1830 and/or the secondoptic cable 1832 terminated thereby.

In one implementation, each of the storage devices 1825, 1835 isimplemented using an EEPROM (e.g., a PCB surface-mount EEPROM). In otherimplementations, the storage devices 1825, 1835 are implemented usingother non-volatile memory device. Each storage device 1825, 1835 isarranged and configured so that it does not interfere or interact withthe communications signals communicated over the media segments 1822,1832.

In accordance with some aspects, the adapter 1810 is coupled to at leasta first media reading interface 1816. In certain implementations, theadapter 1810 also is coupled to at least a second media interface 1818.In some implementations, the adapter 1810 is coupled to multiple mediareading interfaces. In certain implementations, the adapter 1810includes a media reading interface for each port end defined by theadapter 1810. In other implementations, the adapter 1810 includes amedia reading interface for each connection opening 1811 defined by theadapter 1810. In still other implementations, the adapter 1810 includesa media reading interface for each connector arrangement that theadapter 1810 is configured to receive. In still other implementations,the adapter 1810 includes a media reading interface for only a portionof the connector arrangement that the adapter 1810 is configured toreceive.

In some implementations, at least the first media reading interface 1816is mounted to a printed circuit board 1815. In the example shown, thefirst media reading interface 1816 of the printed circuit board 1815 isassociated with the first port end 1812 of the adapter 1810. In someimplementations, the printed circuit board 1815 also can include thesecond media reading interface 1818. In one such implementation, thesecond media reading interface 1818 is associated with the second portend 1814 of the adapter 1810.

The printed circuit board 1815 of the connector assembly 1810 can becommunicatively connected to one or more programmable processors (e.g.,processors 216 of FIG. 2) and/or to one or more network interfaces(e.g., network interfaces 216 of FIG. 2). The network interface may beconfigured to send the physical layer information (e.g., see signals S2of FIG. 1) to a physical layer management network (e.g., seecommunications network 101 of FIG. 1 or IP network 218 of FIG. 2). Inone implementation, one or more such processors and interfaces can bearranged as components on the printed circuit board 1815. In anotherimplementation, one or more such processor and interfaces can bearranged on separate circuit boards that are coupled together. Forexample, the printed circuit board 1815 can couple to other circuitboards via a card edge type connection, a connector-to-connector typeconnection, a cable connection, etc.

When the first connector arrangement 1820 is received in the first portend 1812 of the adapter 1810, the first media reading interface 1816 isconfigured to enable reading (e.g., by the processor) of the informationstored in the storage device 1825. The information read from the firstconnector arrangement 1820 can be transferred through the printedcircuit board 1815 to a physical layer management network, e.g., network101 of FIG. 1, network 218 of FIG. 2, etc. When the second connectorarrangement 1830 is received in the second port end 1814 of the adapter1810, the second media reading interface 1818 is configured to enablereading (e.g., by the processor) of the information stored in thestorage device 1835. The information read from the second connectorarrangement 1830 can be transferred through the printed circuit board1815 or another circuit board to the physical layer management network.

In some such implementations, the storage devices 1825, 1835 and themedia reading interfaces 1816, 1818 each comprise three (3) leads—apower lead, a ground lead, and a data lead. The three leads of thestorage devices 1825, 1835 come into electrical contact with three (3)corresponding leads of the media reading interfaces 1816, 1818 when thecorresponding media segment is inserted in the corresponding port. Incertain example implementations, a two-line interface is used with asimple charge pump. In still other implementations, additional leads canbe provided (e.g., for potential future applications). Accordingly, thestorage devices 1825, 1835 and the media reading interfaces 1816, 1818may each include four (4) leads, five (5) leads, six (6) leads, etc.

FIGS. 4-24 provide an example connector assembly implemented as a firstbladed panel system 1000 suitable for mounting to a communicationsequipment rack. The bladed panel system 1000 includes a chassis 1010configured to receive one or more communications blades 1100. The bladedpanel system 1000 is configured to connect segments of communicationsmedia 1200 carrying communications signals (e.g., signals 51 of FIG. 1).For the sake of convenience, media segments 1200 routed to the rear ofthe chassis 1010 will be referred to herein as “incoming” media segments1211 (FIG. 17) and the media segments 1200 routed to the front of thechassis 1010 will be referred to herein as “outgoing” media segments1212 (FIG. 21). However, each media segment 1211, 1212 may carryincoming signals, outgoing signals, or both.

Each blade 1100 includes one or more communications couplers 1150, eachcoupler defining one or more ports for connecting segments 1211, 1212 ofphysical communications media, which carry communications signals. Insome implementations, each coupler 1150 includes front and rear ports.In accordance with some aspects, the couplers 1150 on an example blade1100 can include fiber optic adapters for connecting optical fibers. Inaccordance with other aspects, the couplers 1150 on another exampleblade 1100 can include communications sockets (e.g., electrical jacks)for connecting electrical plugs (e.g., terminating coaxial cables,twisted pair cables, etc.) to other electrical plugs (e.g., viacorresponding sockets), terminated wires (e.g., via insulationdisplacement contacts), or printed circuit boards (e.g., via contactpins). In accordance with other aspects, the couplers 1150 on an exampleblade 1100 can include transceivers for managing wireless communicationssignals. In accordance with still other aspects, however, the couplers1150 on an example blade 1100 can include some combination of the abovecouplers or other types of communications couplers.

The example bladed panel system 1000 includes PLI functionality as wellas PLM functionality. In accordance with some aspects, the couplers 1150on each blade 1100 include one or more media reading interfaces that areconfigured to read physical layer information stored on or in physicalmedia segments 1200. For example, each coupler 1150 can include a mediareading interface 1305 that communicatively connects to a storage device1230 positioned on or in a physical media segment 1200.

For ease in understanding, one example media segment 1200 including astorage device 1230 storing physical layer information and an examplecoupler 1150 including a media reading interface 1305 configured to readthe physical layer information from the media segment 1200 are discussedare shown in FIGS. 5 and 6, respectively. FIG. 5 shows an examplephysical media segment 1200 implemented as a fiber optic connector(e.g., an LC-type fiber optic connector) 1220 configured to terminate atleast one optical fiber 1210 (FIG. 4). FIG. 6 shows an example coupler1150 implemented as a fiber optic adapter 1300 that is suitable forreceiving media segments, such as the fiber optic connector 1220 of FIG.5. In other implementations, other types of connectors, plugs, adapters,and sockets can be utilized.

The fiber optic connector 1220 includes a body 1221 enclosing an opticalferrule 1222 through which an optical fiber 1210 extends. The body 1221also defines a depression or cavity 1224 in which a storage device 1230can be positioned. In accordance with some implementations, the storagedevice 1230 includes memory circuitry arranged on a printed circuitboard 1231. Electrical contacts 1232 also are arranged on the printedcircuit board for interaction with the media reading interface 1305 ofthe coupler 1150. In one example embodiment, the storage device 1230includes an EEPROM circuit arranged on the printed circuit board 1231.In other embodiments, however, the storage device 1230 can include anysuitable type of non-volatile memory. In the example shown in FIG. 5,the memory circuitry is arranged on the non-visible side of the printedcircuit board 1231.

The fiber optic adapter 1300 includes a body 1301 defining at least oneport 1302 in which a sleeve 1303 is configured to receive and align theferrules 1222 of two fiber optic connectors 1220. Accordingly,communications data signals (e.g., signals 51 of FIG. 1) carried by anoptical fiber terminated by a first of the fiber optic connectors 1220can be transmitted to an optical fiber terminated by a second of thefiber optic connectors 1220.

In some example implementations, the fiber optic adapter 1300 can definea single port 1302 that is configured to optically couple together twofiber optic connectors 1220. In other example implementations, the fiberoptic adapter 1300 can define multiple (e.g., two, three, four, eight,twelve, etc.) ports 1302 that are each configured to optically coupletogether two fiber optic connectors 1220. In other exampleimplementations, each port 1302 is configured to communicatively coupletogether a fiber optic connector 1220 with a media converter (not shown)to convert the optical data signals into electrical data signals,wireless data signals, or other such data signals. In still otherimplementations, the coupler 1150 includes an electrical terminationblock that is configured to receive punch-down wires, electrical plugs(e.g., for electrical jacks), or other types of electrical connectors.

Each fiber optic adapter 1300 also includes at least one media readinginterface 1305 to enable physical layer information to be read from thestorage devices 1230 of the connectors 1220 mounted at the adapter 1300.In certain implementations, the media reading interface 1305 also canwrite physical layer information to the storage device 1230 (e.g., addnew information, delete information, or change/update information). Forexample, in one implementation, the adapter 1300 can include a mediareading interface 1305 associated with each port 1302. In anotherimplementation, the adapter 1300 can include a media reading interface1305 associated with each connection end of a port 1302.

In general, each media reading interface 1305 is formed from one or morecontact members 1310. In some implementations, the adapter body 1301defines slots 1304 configured to receive the one or more contact members1310 (see FIG. 6). In accordance with some aspects, portions of thecontact members 1310 extend into the port 1302 to engage the electricalcontacts 1232 of the storage member 1230 mounted to the fiber opticconnector 1220. Other portions of the contact members 1310 areconfigured to engage contacts on a printed circuit board associated with(e.g., positioned on top of) the fiber optic adapter 1300. As discussedbelow, a processor or other such equipment also can be electricallycoupled to the printed circuit board. Accordingly, such a processor cancommunicate with the memory circuitry on the storage device 1230 via thecontact members 1310 and the printed circuit board.

Additional information pertaining to some example fiber optic connectors1220, storage devices 1230, fiber optic adapters 1300, and contactmembers 1310 can be found in copending U.S. Provisional Application No.61/303,961, filed Feb. 12, 2010, titled “Fiber Plugs and Adapters forManaged Connectivity;” U.S. Application Provisional No. 61/413,828,filed Nov. 15, 2010, titled “Fiber Plugs and Adapters for ManagedConnectivity;” U.S. Provisional Application No. 61/437,504, filed Jan.28, 2011, titled “Fiber Plugs and Adapters for Managed Connectivity,”and U.S. Pat. No. 8,690,593, the disclosures of which are herebyincorporated by reference herein in their entirety.

For example, the example blades 1100 shown in FIG. 7 each include aprocessor 1140 coupled to a printed circuit board (PCB) 1120. Couplers1150 also are mounted (or electrically connected) to the PCB 1120.Accordingly, the processor 1140 on each blade 1100 can communicate withthe media reading interfaces 1305 on the couplers 1150 to manage (e.g.,read, store, update, process, etc.) any physical layer informationassociated with media segments inserted at the couplers 1150. In someimplementations, the blade processor 1140 does not modify, monitor, orotherwise interact with communications signals propagating over mediasegments received at the couplers 1150. In certain implementations, theblade processor 1140 is isolated from the signals carried over the mediasegments. In other implementations, however, each blade 1100 can includean application-specific integrated circuit (ASIC) that can be controlledvia a remote host in place of a processor 1140.

FIG. 7 shows two example communications blades 1100 exploded out from anexample chassis 1010. Each blade 1100 includes a base 1110 and a supportmember 1115. In the example shown in FIG. 7, the base 1110 defines agenerally planar surface and the support member 1115 extends upwardlyfrom a front end of the planar base 1110. The base 1110 includes tabs1105 defining a riding section 1106 and an engagement section 1107 (FIG.12). The communications couplers (e.g., fiber optic adapters, electricalplugs, etc.) 1150 mount to the support member 1115 of the blade 1100(see FIG. 7).

The PCB 1120 mounts to the base 1110. In the implementation shown, thePCB 1120 mounts substantially parallel to the base 1110. In accordancewith some aspects, a central processing unit (e.g., a processor) 1140also can be mounted to the base 1110 and electrically coupled to the PCB1120. In the example implementation shown in FIG. 7, the centralprocessing unit 1140 mounts directly to the PCB 1120 as will bediscussed in more detail herein.

The chassis 1010 includes opposing side walls 1011 interconnected byopposing major surfaces 1012 (see FIGS. 4 and 7) to form a housing 1013defining an interior 1014. In the example shown, the chassis housing1013 defines an open front and an open rear (see FIG. 7). In otherimplementations, one or both of the front and rear can be at leastpartially closed. A management module 1050 also can be mounted to thechassis 1010 to organize one or more of the media segments.

Mounting members 1008 are mounted to the opposing side walls 1011 tofacilitate mounting the chassis housing 1013 to a communications rack.In accordance with one implementation shown in FIG. 7, the mountingmembers 1008 are L-shaped flanges having first sections that attach tothe side walls 1011 and second sections that extend generally parallelwith an open end face of the chassis housing 1013. In other embodiments,however, other types of mounting members 1008 can be used to mount thechassis housing 1013 to a rack. In still other embodiments, other typesof mounting equipment can be used (e.g., to mount the chassis housing1013 to shelves).

Guides 1015 can be provided within the interior 1014 of the chassishousing 1013. The guides 1015 enable the blades 1100 to move relative tothe chassis housing 1013. In certain embodiments, each blade 1100 isconfigured to move separately from the other blades 1100. In certainimplementations, the blades 1100 are configured to travel along theconnector insertion direction. For example, the blades 1100 may beconfigured to travel in a forward-rearward direction.

In some embodiments, the guides 1015 enable each blade 1100 to movebetween at least a first position, in which the blade 1100 is positionedwithin the interior 1014 of the chassis housing 1013, and a secondposition, in which at least a portion of the blade 1100 protrudesoutwardly from the interior 1014 of the chassis housing 1013. Forexample, moving a blade 1100 to the second position can facilitateaccess to the communications couplers 1150 mounted to the blade 1100.

In some embodiments, the guides 1015 are implemented as slides 1020configured to facilitate sliding movement of the blades 1100. FIGS. 8-10illustrate one example slide member 1020 suitable for use as a guide1015. The slide member 1020 includes a body 1021 from which mountingpegs 1022 extend. The mounting pegs 1022 are configured to be receivedwithin openings defined in the sides 1011 of the chassis housing 1013(see FIG. 11). The slide body 1021 defines a longitudinally extendingslot or channel 1024 along a length of the slide body 1021. The channel1024 is sized and configured to receive at least a side edge of theplanar base 1110 of the blade 1100. In certain implementations, thesides of the body 1021 defining the channel 1024 have ramped endportions 1025 to facilitate insertion of the base 1110 into the channel1024.

The slides 1020 can be configured to facilitate lateral sliding of theblades 1100. In some implementations, the slides 1020 are mounted to theopposing side walls 1011 of the chassis 1010 to enable the blades 1100to slide forwardly and rearwardly relative to the chassis 1010. In theexample shown, the slides 1015 are mounted to the chassis housing 1013in a generally parallel, vertically spaced configuration. In otherimplementations, however, the slides 1015 can be configured to enablethe blades 1100 to slide side-to-side or diagonally. In still otherimplementations, other types of guides 1015 are used to facilitate othertypes of blade movement.

In accordance with some aspects, the chassis housing 1013 and the blades1100 are configured to inhibit removal of the blades 1100 from thechassis housing 1013. For example, the chassis housing 1013 can defineone or more stops configured to interact with tabs 1105 on the blade1100 to inhibit movement of the blade 1100 in one or more directions.The stops can be positioned on the side walls 1011 of the chassis 1010adjacent the guides 1015. In some embodiments, at least one stop can beprovided for each guide 1015.

When a blade 1100 is inserted into one of the guides 1015, an edge ofthe blade base 1110 slides into the channel 1024 of the slide 1015. Theriding section 1106 of each tab 1105 seats on top of the slide body 1021and the engagement section 1107 extends upwardly from the riding section1106 to interact with the stops positioned along the side wall 1011 ofthe chassis housing 1013. In the example implementation shown, eachblade 1100 includes two tabs 1105, each extending outwardly from thebase 1110 at a rear of the blade 1100. In other example implementations,the tabs 1105 can extend outwardly from a front of the base 1110 or fromsomewhere between the front and rear of the base 1110. In other exampleimplementations, the tabs 1105 can seat on the bottom of the slide body1021.

In accordance with some aspects of the disclosure, an example chassishousing 1010 can include a forward stop 1017 and a rearward stop 1018associated with each guide 1015. The forward stop 1017 is configured toinhibit forward movement of a blade 1100 beyond a set pull-out distanceto maintain the blade 1100 at least partially within the chassis housing1010 (e.g., see FIG. 11). Accordingly, the blade 1100 can be partiallypulled out of the chassis housing 1013 through the open front to provideaccess to components mounted on the blade 1100.

In some example implementations, the forward stop 1017 is positioned toenable the blade 1100 to be pulled out of the chassis housing interior1014 at least sufficient to provide access to the outgoing physicalmedia segments 1212 received at a front of the communications couplers1150. Indeed, in some example implementations, the forward stop 1017 ispositioned to enable the blade 1100 to be pulled out of the chassishousing interior 1014 at least sufficient to provide access to theincoming physical media segments 1211 received at a rear of thecommunications couplers 1150 (see FIG. 17). In some exampleimplementations, the forward stop 1017 is positioned to enable the blade1100 to be pulled out of the chassis housing interior 1014 at leastsufficient to provide access to the processor 1140 mounted to the blade1100. In one example implementation, the blade 1100 can be pulled outabout three (3) inches.

Likewise, the rearward stop 1018 is configured to inhibit rearwardmovement of the blade 1100 to inhibit the blade 1100 from exiting thechassis housing 1010 through the open rear of the chassis housing 1010(e.g., see FIG. 12). Accordingly, the rear stop 1018 prevents the blade1100 from being unintentionally pushed too far rearward and into thecable manager module 1050. In some example implementations, the rearwardstop 1018 is positioned to inhibit even a rear portion of the blade 1100from exiting the interior 1014 of the chassis housing 1013 through therear end of the chassis housing 1013.

In some embodiments, the chassis housing 1013 is configured to enableinsertion of the blades 1100 optionally through either the open front orthrough the open rear of the chassis housing 1013. In other words, thechassis housing 1013 is configured to enable the user to choose whetherto insert each blade 1100 from the front or from the rear. In oneembodiment, each stop 1017, 1018 defines a ramp on one side and ashoulder on the other. To facilitate insertion, the ramp of the rearwardstops 1018 faces the rear end of the chassis housing 1013 and the rampof the forward stop 1017 faces the open front of the chassis housing1013.

In accordance with some aspects, the blades 1100 can be secured in oneor more positions. For example, in some implementations, the chassishousing 1013 includes retention features to secure each blade 1100 in anextended position and/or a retracted position. In one implementation,the retention feature includes a dimple extending inwardly from the sidewalls 1011. In another implementation, the retention feature includes aspring-mounted ball extending into the chassis 1010. In otherimplementations, other types of retention features can be utilized.

When a blade 1100 is mounted to the chassis housing 1013, the blade 1100is communicatively connected to a network (e.g., see network 218 of FIG.2) for management of any physical layer information associated with thephysical media segments 1200 attached to the blade 1100. In accordancewith some aspects, a backplane 1400 (FIG. 14) is mounted to the chassishousing 1013 to facilitate connecting the blade 1100 to the managementnetwork. In general, the printed circuit boards 1120 on each blade 1100communicatively couple (e.g., electrically couple) to a printed circuitboard 1410 on the backplane 1400 via connector ports 1430. The backplane1400 also includes a network port 1440 via which the backplane 1400connects to the network (FIG. 13).

In some example implementations, the backplane 1400 is mounted at theopen rear of the chassis housing 1013. For example, FIG. 13 shows a rearview of the chassis housing 1013 in which multiple blades 1100 have beenmounted. A rear portion of a backplane 1400 to which the blades 1100 areconnected is visible. The backplane 1400 includes a bracket 1420 thatattaches the printed circuit board 1410 to the chassis housing 1013. Thenetwork port 1440 is mounted to a rear side of the printed circuit board1410 of the backplane 1400. In the example shown, the network port 1440includes a Power Over Ethernet electrical socket configured to receiveDC power source input from the network. In other implementations,however, other types of ports 1440 can be utilized.

FIGS. 14-16 illustrate one example implementation of connecting blades1100 to a backplane 1400. For ease in understanding, select detailspertaining to the chassis housing 1013 and to the blades 1100 have beenremoved from the figures. For example, in FIGS. 14-16, the blades arerepresented by panels 1100′ without differentiating the PCB 1120 fromthe base 1110. Further, the guides 1015 are shows mounted to a genericside wall. Accordingly, details pertaining to the connection between theblades and the backplane 1400 are visible.

In accordance with some implementations, a blade can be connected to thebackplane 1400 using an electrical cable 1450 extending from a first endto a second end. A first electrical connector 1452 is attached to andterminates the first end of the cable 1450 and a second electricalconnector 1454 is attached to and terminates the second end of the cable1450. Each of the connectors 1452, 1454 is configured to plug into amating socket on a printed circuit board. For example, the firstconnector 1452 is configured to plug into (and electrically communicatewith) the printed circuit board 1120 on the blade 1100. The secondconnector 1454 is configured to plug into (and electrically communicatewith) the printed circuit board 1410 on the backplane 1400.

The cable 1450 is sufficiently long to form an at least partial loop(e.g., half loop) 1455 at a location between the first and secondconnectors 1452, 1454. When one of the blades 1100 is pulled forwardlyrelative to the chassis housing 1013, the first connector 1452 of thecorresponding cable 1450 moves with the blade 1100. The second connector1454, however, remains attached to the backplane 1400. Accordingly, thePCBs 1120 mounted to the blades 1100 (and components mounted thereto,e.g., the processor 1140) can remain coupled to the data managementnetwork even when the blades 1100 are moved relative to the chassishousing 1013.

For example, if a user wants to add, remove, or replace a physical mediasegment 1200 on a blade 1100, then the user can slide the blade 1100 toa forward (i.e., or rearward) extended position to access the desiredsegment 1200, coupler port, or other component (e.g., processor 1140)without disconnecting the remaining components on the blade 1100 fromthe data management network. For example, moving the blade 1100 to theextended position and removing a media segment attached to one of thecouplers 1150 does not disconnect the storage devices 1230 of the otherphysical media segments 1200 mounted to the blade 1100 from the network.

In accordance with some aspects of the disclosure, the processors 1140mounted to the blades 1100 can be added, removed, or replaced withoutcompletely removing the blade 1100 from the chassis 1010 ordisconnecting the PCB 1120 from the network. For example, in someimplementations, a blade processor 1140 and the PCB section to which itattaches can be accessed by sliding the blade 1100 from the first bladeposition within the chassis interior 1014 to the second blade positionin which a front of the blade 1100 extends through the open front of thechassis 1010 (e.g., see FIG. 17).

In certain implementations, the blade processor 1140 includes aconnector or socket that is configured to mate with a complementarysocket or connector on the blade PCB 1120. For example, the bladeprocessor 1140 can be secured to the blade PCB 1120 using one or moremezzanine connectors 1142. In the example shown in FIG. 17, the bladeprocessor 1140 is secured to the blade PCB 1120 using two mezzanineconnectors 1142. In other implementations, the blade processor 1140 canbe secured to the PCB 1120 using other types of connectors (e.g.,contact pins).

In some implementations, each blade processor 1140 includes a displayarrangement 1145. For example, in the implementation shown in FIG. 18,each blade processor 1140 includes at least one light emitting diode(LED) 1146. A blade processor 1140 can actuate an LED 1146 to identifythe processor 1140. For example, a user can be directed to a particularblade 1100 by actuating the LED 1146 on the processor 1140. A bladeprocessor 1140 can actuate any additional LEDs 1146 on the blade 1100 toindicate a status (e.g., an error) of the blade 1100, of the processor1140, or of any of the physical segments 1200 attached to the blade1100.

In some implementations, each chassis 1010 is configured to receive afirst blade 1100 having a master processor 1140 and one or moreadditional blades 1100 having a slave processor 1140. Each slaveprocessor is configured to read any physical layer data through thecorresponding media reading interfaces at the direction of the masterprocessor. The master processor coordinates the slave processors andprovides the network connection for the chassis 1010.

In one example implementation, the master processor also includes a userport 1144 through which a user can obtain physical layer informationfrom the master processor and/or can write physical layer data to themaster processor for distribution to one or more physical media storagedevices. One example user port 1144 is shown in FIG. 18. In the exampleshown, the user port 1144 is a USB connector port. In otherimplementations, however, other types of ports (e.g., ports suitable forconnecting to a cell phone, Smartphone, PDA, laptop, or other mobilecomputing device) can be used. In some implementations, only the blade1100 having the master processor includes multiple LEDs 1146, whichprovide status indicia for the entire chassis.

Referring now to FIGS. 19-21, each blade 1100 is configured tofacilitate media segment management and tracking. For example, as shownin FIG. 19, some example implementations of a blade 1100 include afascia 1116 fastened (e.g., screwed, welded, riveted, etc.) to thesupport member 1115 of the blade 1100. The fascia 1116 includes indiciafor identifying particular ones of the couplers 1150 or sets of thecouplers 1150 (e.g., duplex couplers). In the example shown, each fascia1116 includes a number printed above each coupler port. In otherimplementations, other types of indicia (letters, colors, etc. also canbe used).

Some example fascia 1116 can include segment management structures. Forexample, in some implementations, a fascia 1116 can include retentiontabs or fingers 1118 extending forwardly of the fascia 1116. In theexample shown, the fingers 1118 are configured to route communicationscables (e.g., optical fibers, optical fiber cables, electricalconductors, electrical cables, etc.) away from the couplers 1150 along acable routing path (e.g., see FIG. 21).

Referring to FIGS. 22-24, a management module (e.g., cable managementmodule) 1050 can be mounted to the chassis 1010 to organize one or moreof the media segments. Example management modules 1050 have a storagearea 1055 and segment ports 1057. In general, the storage area 1055 isconfigured to store any excess length of one or more physical mediasegments. In particular, the storage area 1055 enables the blades 1100to be moved relative to the chassis 1010 without unplugging incomingcables 1211 from the blades 1100. For example, slack cable length maytighten or loosen around cable spools 1056 positioned at the storagearea 1055 as the blade 1100 is moved forward and rearward relative tothe chassis 1010.

The segment ports 1057 are configured to route physical media segmentsonto and off the management module 1050. In the example shown in FIG.22, the management module 1050 is attached to a rear side of the chassis1010. Accordingly, the management module 1050 is configured to receiveand direct media segments plugged into the rear sides of the couplers1150. For example, each physical media segment plugged into the rearside of the couplers 1150 can be routed rearwardly from the couplers1150, through the storage area 1055, and out the segment ports 1057.

In the example shown, the management module 1050 includes a base 1051having opposing side walls 1052. The base 1051 can include a rearwardlip 1060 to aid in retaining the physical media segments on the module1050. Spools 1056 are mounted at the storage area 1055, which is locatedon the base 1051. Grommets 1058 and seals 1059 are arranged at thesegment ports 1057, which are located on the side walls 1052.

The management module 1050 is configured to removably attach to thechassis housing 1013. In some example implementations, the side walls1052 of the module 1050 include support flanges 1053 and fasteningbrackets 1054. In the example shown, the support flanges 1053 defineL-shaped members, which are oriented in an outwardly (sideways) facingdirection. In other example embodiments, the module support flange 1053also could be oriented in a downwardly pointing direction. The fasteningbrackets 1054 define through-holes.

The chassis housing 1013 includes complementary features including asupport flange 1003 and a fastening bracket 1004 (FIG. 22). The supportflange 1003 of the chassis housing 1013 is oriented in an upwardlypointing direction. In other example embodiments, the chassis supportflange 1003 also could be oriented in an outwardly (sideways) facingdirection. The fastening brackets 1004 define through-holes.

To attach the management module 1050 shown in FIG. 22 to the chassishousing 1013, the support flanges 1053 of the management module 1050 isseated on the support flange 1003 of the chassis housing 1013. Engagingthe support flanges 1053, 1003 with each other positions the brackets1054, 1004 to align the through-holes. A fastener (e.g., a screw, abolt, a rivet, etc.) can be inserted through the holes in the brackets1054, 1004 to secure the management module 1050 to the chassis 1010. Inother implementations, the management module 1050 can be welded, glued,or otherwise secured to the chassis 1010.

To enhance clarity of the application, the following disclosure providesan example walk-through of routing the incoming and outgoing mediasegments 1211, 1212 for an example blade 1100. One or more chasses 1010are provided, for example, on an equipment rack. One or more blades 1100are installed in each chassis 1010. Circuit boards on each blade 1100may be connected to a backplane 1400 of the chassis 1010 (e.g., bysliding the blade into the chassis 1010 towards the backplane 2014). Aprocessor 1140 on each blade 1100 is connected to the backplane 1400 viathe circuit boards.

Incoming cables 1211 are connected to each blade 1100 after the blade1100 has been inserted into the chassis 1010. For example, a technicianmay secure the incoming cables 1211 at the management region 1050 at therear of the chassis 1010. In some implementations, the incoming cables1211 include optical fibers separately terminated by a fiber opticconnector (e.g., an LC-type connector). In other implementations, theincoming cables 1211 include one or more multi-fiber cables, each ofwhich is terminated by a multi-fiber connector (e.g., an MPO-typeconnector).

The technician plugs connectorized ends of the incoming cables 1211 intothe rear ports of the blade 1100. For example, the technician may feedconnectorized ends of the incoming cables 1211 from the rear of thechassis 1010, over the base 1110 of the blade 1100, toward the adapters1151. The technician may subsequently access the adapters 1151 throughan open top of the blade 1100 at the front of the chassis 1010 (see FIG.17). For example, the technician may access the adapters 1151 with theblade 1100 in the first or second extended position. In particular, thetechnician can unplug a dust plug from one of the rear ports of theadapters 1151 and insert one of the connectorized ends into the rearport from the front of the chassis 1010.

Subsequently, outgoing cables 1212 can be installed at the front portsof the blade 1100 without disconnecting the blade 1100 from thebackplane 1400. In some implementations, the outgoing cables 1212include optical fibers separately terminated by a fiber optic connector(e.g., an LC-type connector). In other implementations, the outgoingcables 1212 include one or more multi-fiber cables, each of which isterminated by a multi-fiber connector (e.g., an MPO-type connector). Incertain implementations, the technician may plug the connectors 1220 ofthe outgoing cables 1212 into the front ports of the adapters 1151 whenthe blade 1100 is in the closed or first extended position. In otherimplementations, however, the connectors 1220 of the outgoing fibers1212 may be plugged into the front adapter ports while the blade 1100 isin any desired position. The technician also routes the fibers 1220through the retention fingers 1118 at the front of the blade 1100.

FIGS. 25-44 provide another example connector assembly implemented as abladed panel system 2000 suitable for mounting to a communicationsequipment rack. The bladed panel system 2000 includes a chassis 2010configured to receive one or more communications blades 2100. The bladedpanel system 2000 is configured to connect segments of communicationsmedia 2200 carrying communications signals (e.g., signals 51 of FIG. 1).For the sake of convenience, media segments 2200 routed to the rear ofthe chassis 2010 will be referred to herein as “incoming” media segments2210 (FIG. 40) and the media segments 2200 routed to the front of thechassis 2010 will be referred to herein as “outgoing” media segments2220 (FIG. 41). However, each media segment 2210, 2220 may carryincoming signals, outgoing signals, or both.

In the example shown in FIG. 25, the chassis housing 2010 issubstantially similar to the chassis housing 1010 shown in FIGS. 4 and7, including opposing side walls 2011 interconnected by opposing majorsurfaces 2012 to form a housing 2013 defining an interior 2014. Thechassis housing 2013 defines an open front and an open rear (see FIG.27). In other implementations, one or both of the front and rear can beat least partially closed. The chassis housing 2013 includes mountingmembers 2008 and guides 2015 that enable the blades 2100 to moverelative to the chassis housing 2013. For example, the blades 2100 maybe configured to move along a connector insertion direction (e.g.,forwardly and rearwardly). The chassis housing 2013 also includesforward stops 2017 and rearward stops 2018 to inhibit removal of theblades 2100 from the chassis housing 2013.

A management module 2050 (FIG. 26) also can be mounted to the chassis2010 to organize one or more of the media segments. In certainimplementations, the management module 2050 also is configured to enablethe blades 2100 to be moved relative to the chassis 2010 withoutunplugging incoming cables 2210 from the blades 2100. For example, slackcable length may tighten or loosen around cable spools 2056 positionedat a storage area 2055 of the management module 2050 as the blade 2100is moved forward and rearward relative to the chassis 2010.

In certain implementations, the management module 2050 may besubstantially similar to the management module 1050 shown in FIGS.22-24, including a base 2051 having opposing side walls 2052. The base2051 can include a rearward lip 2060 to aid in retaining the physicalmedia segments on the module 2050. Spools 2056 are mounted at thestorage area 2055, which is located on the base 2051. Grommets 2058 andseals 2059 are arranged at the segment ports 2057, which are located atthe rear of the management module 2050.

The example bladed panel system 2000 includes PLI functionality as wellas PLM functionality. As shown in FIG. 27, the chassis 2010 includes abackplane 2400 to facilitate connecting the blades 2100 to a datamanagement network (e.g., an Internet Protocol network). The backplane2400 includes a printed circuit board 2410 including connector ports2430, via which blades 2100 connect to the backplane 2400, and a networkport (not shown) via which the backplane 2400 connects to the network.The printed circuit board 2410 is supported by bracket 2420, whichcouples to the chassis housing 2010.

FIGS. 28-30 illustrate one example implementation of a blade module2100. Each blade 2100 includes one or more communications couplers 2150,each coupler 2150 defining one or more ports for connecting segments ofphysical communications media, which carry communications signals. Incertain implementations, the couplers 2150 include media readinginterfaces that are configured to read physical layer information fromstorage devices on or in a connectorized media segments plugged into thecouplers 2150. Adapter 1300 of FIG. 6 is one example implementation of acoupler 2150. Connector 1220 of FIG. 5 is one example implementation ofa connectorized end 1220 of a media segment. Additional examples ofcouplers and connectorized media segments are disclosed in U.S.Provisional Application Nos. 61/303,961; 61/413,828; 61/437,504; andU.S. Pat. No. 8,690,593 incorporated by reference above.

The blade 2100 includes a base 2110 configured to ride within the guides2015 of the chassis housing 2010. A support member 2115 extends upwardlyfrom a front end of the base 2110. Communications couplers (e.g., fiberoptic adapters, electrical plugs, etc.) 2150 mount to the support member2115. A printed circuit board (PCB) arrangement 2120, which is discussedin greater detail herein, and a processor (e.g., a microprocessor) 2140also are mounted to the blade 2100. In some implementations, the bladeprocessor 2140 does not modify, monitor, or otherwise interact withcommunications signals propagating over media segments received at thecouplers 2150. In certain implementations, the blade processor 2140 isisolated from the signals carried over the media segments. Rather, theblade processor 2140 is configured to manage data signals stored inmemory devices of the media segments.

The base 2110 of each blade 2100 includes outwardly extending tabs 2105that are configured to ride within the chassis guides 2015 and tointeract with the stops 2017, 2018. For example, the tabs 2105 candefine a riding section 2106 and an engagement section 2107 thatfunction the same as the riding and engagement sections 1106, 1107 oftabs 1105 discussed above. The base 2110 also can include an outwardlyextending tab 2108 to facilitate moving the blade 2100 along the guides2015. For example, the tab 2108 can define a forwardly extending handlewith which a user can manipulate movement of the blade 2100.

In certain embodiments, each blade 2100 is configured to move separatelyfrom the other blades 2100. In some embodiments, the guides 2015 enableeach blade 2100 to move between at least a first position, in which theblade 2100 is positioned within the interior 2014 of the chassis housing2013 (e.g., FIG. 31), and a second position, in which at least a portionof the blade 2100 protrudes outwardly from the interior 2014 of thechassis housing 2013 (e.g., FIG. 32). In some embodiments, the guides2015 are implemented as slides configured to facilitate sliding movementof the blades 2100. In the example shown, the slides 2015 are mounted tothe opposing side walls 2011 of the chassis 2010 to enable the blades2100 to slide forwardly and rearwardly relative to the chassis 2010.

In accordance with some aspects, the blades 2100 can be secured in oneor more positions. Securing a blade 2100 in a particular position canfacilitate access to the communications couplers 2150 and/or a processor2140 mounted to the blade 2100. For example, securing the blade 2100 inposition inhibits the removal of the blade 2100 when adding, removing,or replacing blade couplers 2150 and/or the blade processor 2140. Insome implementations, the chassis housing 2013 includes retentionfeatures (e.g., as described above with respect to chassis housing 1013)to secure each blade 2100 in an extended position and/or a retractedposition.

In accordance with some aspects, the communications couplers 2150 ofeach blade can remain coupled to the data management network (e.g., viathe backplane 2400) even when the blade 2100 is moved relative to thechassis housing 2013 (e.g., to a position in which at least part of theblade 2100 extends outwardly from the chassis interior 2014). Thecommunications couplers 2150 are connected to the backplane 2400 via thePCB arrangement 2120 of the blade and the PCB 2020 of the chassis.

In accordance with some implementations, the PCB arrangement 2120 ofeach blade 2100 can include at least a first printed circuit board 2122and a second printed circuit board 2124. The communications couplers2150 are coupled to first printed circuit board 2122 and the backplane2400 is coupled to the second printed circuit board 2124. In the exampleshown, the second printed circuit board 2124 is connected to thebackplane 2400 via a card edge connection 2125 (FIG. 29). In otherimplementations, the second printed circuit board 2124 can be connectedto the backplane 2400 via other types of connections (e.g., aplug/socket connection, a cable connection, a wireless connection,etc.).

The printed circuit boards 2122, 2124 are configured to move relative toeach other. For example, in some implementations, the second printedcircuit board 2124 is configured to slide within a guide arrangement2160 mounted to the blade base 2110. The guide arrangement 2160 includesopposing guides 2161 bordered by stops 2162 at opposite ends. In theexample shown, the second printed circuit board 2124 includes arms 2127that are configured to slide within channels 2163 defined by the guides2161. The stops 2162 at the ends of the guides 2161 inhibit removal ofthe second printed circuit board 2124 from the guides 2161.

The first printed circuit board 2122 is connected to the second printedcircuit board 2124 using an electrical cable 2450, which extends from afirst end to a second end. A first electrical connector 2452 is attachedto and terminates the first end of the cable 2450 and a secondelectrical connector 2454 is attached to and terminates the second endof the cable 2450. The first connector 2452 is electrically coupled(e.g., via contact pins) to the first printed circuit board 2122 and thesecond connector 2452 is electrically coupled (e.g., via contact pins)to the second printed circuit board 2124.

The cable 2450 is sufficiently long to enable the second printed circuitboard 2124 to move along the guide channels 2163 relative to the firstprinted circuit board 2122 without disconnecting from the first printedcircuit board 2122. For example, when the second printed circuit board2124 is positioned at a first end of the channels 2161 (e.g., as shownin FIG. 28), the cable 2450 can form a half loop 2455 at a locationbetween the first and second connectors 2452, 2454. When the secondprinted circuit board 2124 is positioned at a second end of the channels2161 (e.g., as shown in FIG. 29), the cable 2450 straightens out toextend over the distance between the printed circuit boards 2122, 2124.

In use, the guide arrangement 2160 can be configured so that the secondprinted circuit board 2124 is located at the first end of the guides2161 when the blade 2100 is located in the first position within theinterior 2014 of the chassis 2010. The guide arrangement 2160 also canbe configured so that the second printed circuit board 2124 is locatedat the second end of the guides 2161 when the blade 2100 is located inthe second position protruding outwardly from the interior 2014 of thechassis 2010.

Accordingly, when a user chooses to pull one of the blades 2100forwardly relative to the chassis housing 2013 (e.g., to access acommunications coupler or to access the processor 2140), the firstconnector 2452 of the corresponding cable 2450 moves with the blade2100. The second connector 2454, however, remains attached to thebackplane 2400. For example, if a user wants to add, remove, or replacea physical media segment 1200 on a blade 2100, then the user can slidethe blade 2100 to a forwardly extended position to access the desiredsegment 1200 or coupler port without disconnecting the storage devices1230 of the remaining physical media segments 1200 mounted to the blade2100 from the data management network.

In one implementation, the amount of force necessary to overcome theretention feature 2016, which inhibits removal of the blade 2100 fromthe chassis 2010, is sufficient to overcome the connection between thesecond printed circuit board 2124 and the backplane 2400. For example,the force necessary to overcome the retention feature 2016 is sufficientto disconnect a card edge connection between the second printed circuitboard 2124 and the backplane 2400.

As noted above, moving a blade 2100 to a position at least partiallyoutside the chassis 2010 facilitates access to components on the blade2100. For example, moving the blade to such an extended position canfacilitate access to a processor 2140 mounted to the blade. Inaccordance with certain aspects of the disclosure, the processors 2140mounted to the blades 2100 can be added, removed, or replaced withoutcompletely removing the blade 2100 from the chassis 2010.

In certain implementations, the blade processor 2140 includes aconnector or socket that is configured to mate with a complementarysocket or connector on the first printed circuit board 2122 of the blade2100. For example, the blade processor 2140 can be secured to the firstprinted circuit board 2124 using a snap-fit connection (see FIGS. 33 and36). In other implementations, the blade processor 2140 can be securedto the first printed circuit board 2122 using other types of connectors(e.g., cable, mezzanine, etc.).

In accordance with some aspects of the disclosure, the backplane 2400 ofthe chassis 2010 connects to the data network via a chassis processor2600. The chassis processor 2600 functions as the interface between thepanel system 2000 and the data management network. In someimplementations, the chassis processor 2600 manages the blade processors2140. For example, the chassis processor 2600 can instruct each of theblade processors 2140 to determine which communications couplers 2150have media segments inserted therein, to obtain physical layerinformation from the media segments, and to forward the physical layerinformation to the chassis processor 2600 for storage and/ortransmission to the data network. In one implementation, the chassisprocessor 2600 has a master/slave relationship with the blade processors2140.

The chassis processor 2600 is configured to mount to the chassis housing2013. For example, in some implementations, the chassis processor 2600can mount to a support structure 2070 extending outwardly from a top,rear of the chassis housing 2013 (e.g., see FIG. 35). The supportstructure 2070 includes a top 2071 and side walls 2072 defining aninterior that is sized and configured to receive the chassis processor2600. Support flanges 2073, which extend outwardly from the side walls2072, define through openings 2074. The chassis processor 2600 includesa base 2610 and a fascia 2612 extending generally perpendicular to thebase 2610. The fascia 2612 defines openings through which fasteners 2615(e.g., set screws) can extend. The fasteners 2615 also extend throughthe openings defined in the support flanges 2073 of the supportstructure 2070 to secure the chassis processor 2600 to the supportstructure 2070.

The chassis processor 2600 includes a printed circuit board 2620 mountedto the base 2610 (e.g., using fasteners 2614). The printed circuit board2620 of the chassis processor 2600 is configured to connect to theprinted circuit board 2410 of the backplane 2400 (e.g., via a card edgeconnection, via a plug/socket connection, via a cable connection, etc.).Memory (e.g., an EEPROM chip) and other electronic circuitry can bemounted to the printed circuit board 2620. Physical layer informationobtained by the communications couplers 2150 can be stored in the memoryof the chassis processor 2600.

In accordance with some implementations, the fascia 2612 of the chassisprocessor 2600 includes one or more indicators (e.g., light emittingdiodes) 2650 (e.g., see FIG. 35). The indicators 2650 can display statusinformation (e.g., error information, power information, networkconnection information, etc.).

A first network port 2630 is electrically connected to the printedcircuit board 2620 of the chassis processor 2600. In the example shown,the first network port 2630 defines an RJ jack configured to receive anelectrical plug 2232 terminating a PLI cable 2230 (FIG. 36) connectingthe panel system 2000 to the data network (e.g., network 218 of FIG. 2,network 101 of FIG. 1, etc.). In other implementations, however, thefirst network port 2630 can define a USB socket or other type of cableport.

In accordance with certain aspects, a second port 2640 also can beconnected to the printed circuit board 2620. In the example shown, thesecond port 2640 defines a DC power socket. In other implementations,however, the second port 2640 can define any suitable type of powercable port. In some implementations, the second port 2640 provides analternative port by which the panel system 2000 can receive power froman auxiliary power source (e.g., when Power Over Ethernet is notavailable).

In accordance with some aspects of the disclosure, the chassis 2010 caninclude one or more data ports 2730 (e.g., see FIG. 37) configured toenable connecting a mobile device to the storage devices on any mediasegments plugged into the communications couplers 2150. The data port2730 enables a user to connect (e.g., using a communications cable) amobile device (e.g., a handheld scanner, a cell phone, a Smartphone, aPDA, a laptop, etc.) to the panel system 2000. For example, a user candownload physical layer information about the media segments connectedto the communications couplers 2150 of the panel system 2000 from thechassis processor 2600 to memory on the mobile device.

The user also can use the mobile device to manipulate (e.g., add,delete, and/or change) the physical layer information stored on thechassis processor 2600. For example, the user can upload new and/orupdated physical layer information (e.g., test results) from the mobiledevice to the chassis processor 2600. In accordance with certainaspects, the user can upload physical layer information pertaining tomedia segments that are connected to the communications couplers 2150but are not associated with storage devices (i.e., do not otherwise havePLI and PLM functionality).

In some implementations, each blade processor 2140 defines such a dataport 2730. In other implementations, the chassis 2010 is configured toreceive a status board 2700 defining such a data port (see FIG. 37). Forexample, the status board 2700 can slide into the chassis housing 2013from a front of the chassis 2010. The status board 2700 includes afascia 2720 mounted to one end of a printed circuit board 2710. In theexample shown, the fascia 2720 defines openings 2722 through whichfasteners 2725 can extend to be received in openings 2704 defined bymounting tabs 2702 of the chassis housing 2013 (see FIGS. 37 and 38). Incertain implementations, the printed circuit board 2710 slides alongguides mounted within the chassis housing 2013. In otherimplementations, the status board 2700 can be otherwise secured to thechassis 2010.

The data port 2730 mounts to the fascia 2720 and electrically connectsto the printed circuit board 2710. The other end of the printed circuitboard 2710 is configured to connect to the printed circuit board 2410 ofthe backplane 2400. In the example shown, the printed circuit board 2710includes a card edge connector 2715 that plugs into the printed circuitboard 2410 of the backplane 2400. In other implementations, the printedcircuit board 2710 can connect to the backplane 2400 using a differenttype of electrical connector. Accordingly, a mobile device (i.e., asdiscussed above) can be plugged into the panel system 2000 and/or datanetwork from the front of the chassis 2010.

Additional components also can be mounted to the status board 2700. Forexample, indicators (e.g., LEDs) 2726 can be positioned on the fascia2720. The LEDs 2726 can display status information (e.g., errorinformation, power information, network connection information, etc.)for the chassis 2010. An indicator 2415 on a front of each bladeprocessor 2140 can identify or display a status for the individual blade2100.

In some implementations, a switch (i.e., or other input mechanism) 2728is positioned on the fascia 2720. In accordance with some aspects, theinput mechanism 2728 can include a momentary pushbutton signal to thechassis processor 2600. In other implementations, the input mechanism2728 can include a fixed position slide or a pushbutton switch forparticular signal configuration indications to the chassis processor2600.

As shown in FIGS. 39-41, a fascia 2116 can be mounted to the supportstructure 2115 of each blade 2100. In some implementations, the fascia2116 includes indicia for identifying particular ones of thecommunications couplers 2150 or sets of the couplers 2150 (e.g., duplexcouplers, quad couplers, etc.). In one implementation, each fascia 2116includes a number printed above each coupler port. In anotherimplementation, each fascia 2116 includes a number printed above eachpredefined set of coupler ports. In other implementations, however,other types of indicia (letters, colors, etc.) can be used.

The fascia 2116 defines a stepped portion 2117 that is sized andconfigured to accommodate the blade processor 2140 so that the indicator2145 on the blade processor 2140 is visible from the front. The steppedportion 2117 of each blade fascia 2116 also is sized and configured toaccommodate the status board 2700 so that the fascia 2720 of the statusboard 2700 is visible from the front of the chassis 2010. Accordingly,the data port 2730 and indicators 2726 are accessible to a user (seeFIG. 39).

Some example fascia 2116 can include segment management structures. Forexample, in some implementations, a fascia 2116 can include retentionmembers or fingers 2118 extending forwardly of the fascia 2116 (see FIG.40). In the example shown, the fingers 2118 are configured to routecommunications cables (e.g., optical fibers, optical fiber cables,electrical conductors, electrical cables, etc.) away from thecommunications couplers 2150 along a cable routing path (e.g., see FIG.41).

In the example shown, each retention member 2118 includes opposingretaining members 2181 interconnected by side members 2182 to define athrough passage. A rib 2183 extends between the retaining members 2181within the through passage to define a cable routing passage 2185 (FIG.40). One of the retaining members 2181 defines a slot 2184 leading tothe cable routing passage 2185. In the example shown, the slot 2184 isdefined in a top retaining member 2181 of each retention member 2118. Inother implementations, the slot 2184 can be defined in one of the sidemembers 2182. In still other implementations, the slot 2184 can beclosed by a flexible or removable bridge.

One or more segments of physical communications media can be routed fromthe communications couplers 2150, through the cable routing passages2185 defined by the retaining members 2181, to the sides of the chassis2010. In some implementations, the outermost retention members 2118 haveretaining members 2181′ that define ramped or curved inner surfaces tofacilitate routing the media segments. For example, the curved innersurfaces of the retaining members 2181′ can inhibit excessive bending ofoptical media segments.

Referring to FIGS. 42-44, the management module 2050 can be secured to arear side of the chassis housing 2010 without components protrudingoutwardly from the management module 2050. Having a substantially planarinterface between the chassis housing 2010 and the management module2050 on each side can facilitate insertion of the panel system 2000 intoan equipment rack or other suitable support structure.

In the example shown, the management module 2050 includes retainingmembers 2062 that are configured to slide over a tab 2005 of the chassishousing 2010. The tab 2005 defines an opening 2006 into which a lug 2064of the management module 2050 can snap to secure the components together(see FIG. 44). In the implementation shown in FIG. 42, the tabs 2062 andlug 2064 are punched out from the side walls 2052 of the managementmodule 2050.

To enhance clarity of the application, the following disclosure providesan example walk-through of routing the incoming and outgoing mediasegments 2200 for an example blade 2100. One or more chasses 2010 areprovided, for example, on an equipment rack. One or more blades 2100 areinstalled in each chassis 2010. A circuit board arrangement 2120 on eachblade 2100 may be connected to a backplane 2410 of the chassis 2010(e.g., by sliding the blade 2100 rearwardly into the chassis 2010). Forexample, a second circuit board 2124 on each blade 2100 may be connectedto the backplane 2410 (e.g., via a card-edge connection, via aconnector, etc.). The processor 2140 on each blade 2100 is connected tothe backplane 2410 via the circuit board arrangement 2120.

Incoming cables 2210 are connected to each blade 2100 after the blade2100 has been inserted into the chassis 2010. For example, a technicianmay secure (e.g., using a cable tie) the incoming cables 2210 to themanagement structures (cable spools, cable clamp, fanout arrangement, orother securement structure) of the management region 2050. Thetechnician plugs connectorized ends of the incoming cables 2210 into therear ports of the blade 2100. In some implementations, the incomingcables 2210 include optical fibers separately terminated by a fiberoptic connector (e.g., an LC-type connector). In other implementations,the incoming cables 2210 include one or more multi-fiber cables, each ofwhich is terminated by a multi-fiber connector (e.g., an WO-typeconnector).

The technician routes the connectorized ends of the incoming cables 2210to the rear ports of the blade 2100. In certain implementations, thetechnician feeds connectorized ends of the incoming cables 2210 from therear of the chassis 2010, over the base 2110 of the blade 2100, towardthe front adapters 2151. In some implementations, the technician plugsthe connectorized ends of the incoming cables 2210 into the rear portsfrom the rear of the chassis 2010. In other implementations, thetechnician may subsequently access the adapters 2151 through an open topof the blade 2100 at the front of the chassis 2010. For example, thetechnician may access the adapters 2151 with the blade 2100 in the firstor second extended position. In particular, the technician can unplug adust plug from one of the rear ports of the front adapters 2151 andinsert one of the connectorized ends into the rear port from the frontof the chassis 2010 (see FIG. 40).

Subsequently, outgoing cables 2220 can be installed at the front portsof the blade 2100 without disconnecting the blade 2100 from thebackplane 2410. For example, the technician may plug the connectorizedends of the outgoing cables 2220 into the front ports of the adapters2151 when the blade 2100 is in the closed or first extended position. Inother implementations, however, the connectorized ends of the outgoingfibers 2220 may be plugged into the front adapter ports while the blade2100 is in any desired position. The technician also routes the outgoingcables 2220 through the retention fingers 2118 at the front of the blade2100.

FIGS. 45-150 provide other example connector assemblies implemented asbladed panel systems 3000 suitable for mounting to communicationsequipment racks, cabinets, or other structures. The bladed panel system3000 includes a chassis 3010 configured to receive one or morecommunications blades 3100. The bladed panel system 3000 is configuredto connect segments of communications media 3200 carrying communicationssignals (e.g., signals S1 of FIG. 1). In accordance with some aspects,the example bladed panel system 3000 includes PLI functionality as wellas PLM functionality. For example, the bladed panel system 3000 isconfigured to read physical layer information (e.g., signals S2 ofFIG. 1) from one or more of the media segments 3200.

In some implementations, each blade 3100 includes one or more mediacouplers 3150 that are configured to connect together media segments3200 and to read physical layer information from the media segments3200. For example, the media couplers 3150 may connect segments 3200received at a rear of the chassis 3010 with segments 3200 received at afront of the chassis 3010. For the sake of convenience, media segments3200 routed to the rear of the chassis 3010 will be referred to hereinas “incoming” media segments 3210 and the media segments 3200 routed tothe front of the chassis 3010 will be referred to herein as “outgoing”media segments 3220. However, each set of media segments 3200 may carryincoming signals, outgoing signals, or both.

One example chassis 3010 is shown in FIGS. 45-49. The chassis 3010 issimilar to the chassis housings 1010, 2010 shown in FIGS. 7 and 27,including opposing side walls 3011 interconnected by opposing majorsurfaces 3012 to form a housing 3013 defining an interior 3014. Thechassis housing 3013 defines an open front and an open rear. In otherimplementations, one or both of the front and rear can be at leastpartially closed. The chassis housing 3013 includes a grounding port3007 at which a grounding wire or cable may enter the chassis housing3013.

The chassis housing 3013 includes mounting brackets 3008 to secure thechassis housing 3013 to the rack, poles, or other structures. In someimplementations, the mounting brackets 3008 extend along only a portionof the side walls 3011 of the chassis 3010 (e.g., see FIG. 77). In otherimplementations, the mounting brackets 3008 extend along a majority ofthe side walls 3011 of the chassis 3010 (see FIGS. 45-47). In theexamples shown, the brackets 3008 are L-shaped. In otherimplementations, however, other types of mounting brackets may be used.

The interior 3014 of the chassis housing 3013 includes guides 3015 thatenable the blades 3100 to move (e.g., slide forwardly and rearwardly)relative to the chassis housing 3013. For example, the guides 3015 mayenable the blades to each move from a closed (retracted) position to oneor more extended positions relative to the chassis 3010. In certainimplementations, the guides 3015 are substantially the same as guidingslots 1020 of FIGS. 8-10. In other implementations, however, other typesof guides can be used.

In some implementations, the chassis 3010 is configured to receive astatus board 3070 (FIG. 45). The status board 3070 includes a fascia3071 mounted to one end of a printed circuit board (e.g., see statusboard 2700 of FIG. 37). The status board 3070 also may include a base toprotect the printed circuit board. In certain implementations, theprinted circuit board slides along guides mounted within the chassishousing 3013. For example, the status board 3070 can slide into theguides from a front of the chassis 3010. In other implementations, thestatus board 3070 can be otherwise secured to the chassis 3010.

In some implementations, the fascia 3171 of the status board 3070defines openings 3172 through which fasteners can extend to secure thestatus board 3070 to the chassis housing 3013 (see FIG. 45). Indicators(e.g., LEDs) 3076 also can be positioned on the fascia 3071 of thestatus board 3070. The LEDs 3076 can display status information (e.g.,error information, power information, network connection information,etc.) for the chassis 3010. In some implementations, a switch (i.e., orother input mechanism) also may positioned on the fascia 3071.

The rear of the chassis 3010 is configured to facilitate routing andsecurement of the incoming media segments 3210. FIG. 47 is a rearperspective view of the chassis housing 3013 showing various examplemanagement structures. FIGS. 77-79 also show rear perspective views ofchassis 3010 with various management structures. Non-limiting examplesof management structures include cable retention clamps 3030, cableretention fingers 3034 (FIG. 79), and cable fanouts 3035 (FIG. 77). Inother implementations, other types of management structures (e.g.,spools, radius limiters, cable ties, etc.) may be utilized at the rearof the chassis 3010.

In FIG. 47, cable retention clamps 3030 are shown attached to thechassis housing 3013 on the right side of the drawing. The example cableretention clamps 3030 include compression inserts 3031 through whichmedia segments 3200 can be routed. The insert 3031 may include a slot tofacilitate routing of the media segments 3200 through the insert 3031.The cable retention clamps 3030 also include compression members 3032that mount to either side of the insert 3031 to clamp down on the insert3031. The cable clamps 3030 may be attached to the chassis housing 3013with brackets 3033.

An example fanout arrangement 3035 is shown in FIG. 47 attached to thechassis housing 3013 on the left side of the drawing. The fanoutarrangement 3035 includes a mounting panel 3036 on which one or morefanouts 3037 can be installed. For example, one or more fanouts 3037 caninclude openings through which pins 3038 may extend to mount the fanouts3037 to the panel 3036. Multiple fanouts 3037 can be stacked onto oneset of pins 3038. Each fanout 3037 is configured to separate a mediasegment 3200 into multiple segments. For example, each fanout 3037 mayseparate a multiple fiber cable into individual fibers. In certainimplementations, each of the individual fibers is terminated at a fiberoptic connector.

In some implementations, one or more retention clamps 3030 can bepositioned on each side of the chassis 3010 at the rear. In otherimplementations, one or more fanout arrangements 3035 can be positionedon each side of the chassis 3010 at the rear. In certainimplementations, each side of the chassis 3010 holds at least oneretention clamp 3030 and at least one fanout arrangement 3035. Inaccordance with some aspects, the management structures are configuredto be releasably attached to the chassis housing 3013 so that anappropriate management structure may be attached to the chassis housing3013 in the field. In other implementations, other types of fanoutconfigurations may be utilized.

Which management structure 3030, 3035 is appropriate may depend on thetypes of incoming media segments 3210 and the configuration of thecoupler arrangement installed on each blade 3100 to be held within thechassis 3010. In some implementations, the clamps 3030 may beappropriate if the incoming media segments 3210 are terminated byconnectors 3212 that is configured to be received within couplers 3151,3153, 3155 of the coupler arrangement 3150. For example, a cable clamp3030 may be appropriate when a multi-fiber cable 3210 terminated by anMPO connector 3212 is to be plugged into an MPO coupler 3153, 3155 (seeFIGS. 65 and 77). In other implementations, the fanout arrangements 3035may be appropriate if the incoming media segments 3210 are multi-fiberconnectors that are to be plugged into LC-adapters. In suchimplementations, the fanout arrangements 3035 may separate themulti-fiber cables into individual fibers terminated by LC connectorsthat may be plugged into the LC adapters.

The chassis 3010 also includes a chassis processor 3060 that functionsas the interface between the panel system 3000 and the data managementnetwork. The chassis processor 3060 may be connected to a backplane 3040to manage the media reading interfaces, either directly or viaprocessors on the individual blades 3100. The chassis processor 3060also may connect the backplane 3040 to the data management network. Incertain implementations, the chassis processor 3060 also may includememory (e.g., an EEPROM chip) and other electronic circuitry so thatphysical layer information obtained at the blades 3100 can be stored inthe memory of the chassis processor 3060.

In some implementations, the chassis processor 3060 includes a printedcircuit board 3061 (FIG. 48) that is configured to connect to the port3044 (FIG. 77) of the backplane 3040. For example, the circuit board3061 may include a connection edge 3062 that is configured to connect toport 3044 via a card edge connection. In other implementations, thecircuit board 3061 may otherwise connects to the port 3044 (e.g., via aplug/socket connection, via a cable connection, etc.).

The chassis processor 3060 is configured to mount to the chassis housing3013. For example, in some implementations, the chassis processor 3060can mount to a support structure 3020 extending outwardly from a top,rear of the chassis housing 3013 (e.g., see FIG. 47). The supportstructure 3020 includes a top 3021 and side walls 3022 defining aninterior that is sized and configured to receive the chassis processor3060. In certain implementations, the interior of the support structure3020 includes guides 3025 along which the printed circuit board 3062 mayslide (FIG. 48).

In certain implementations, the chassis processor 3060 includes a fascia3063 coupled to the circuit board 3061. In some implementations, thefascia 3063 is configured to connect to mounting flanges 3023 (FIG. 47)extending inwardly from the side walls 3022 of the support structure3020. For example, the fascia 3063 may mount to the flanges 3023 viafasteners 3064 (FIG. 49), via a snap-fit connection, or via other typesof attachment members. In other implementations, the chassis processor3060 may be otherwise secured to the chassis 3010.

In some implementations, a first network port 3065 is electricallyconnected to the circuit board 3061 of the chassis processor 3060. Forexample, the first network port 3065 may define an RJ jack configured toreceive an electrical plug terminating a network data cable connectingthe panel system 3000 to the data network. In other implementations,however, the first network port 3065 can define a USB socket or othertype of cable port.

In certain implementations, the chassis processor 3060 also may includea second port 3067. For example, the second port 3067 may defines a DCpower socket or any suitable type of power cable port. In someimplementations, the second port 3067 provides an alternative port bywhich the panel system 3000 can receive power from an auxiliary powersource (e.g., when Power Over Ethernet is not available).

The chassis processor 3060 also may control one or more indicators(e.g., light emitting diodes) 3066 mounted to the fascia 3063. Theindicators 3066 can display status information (e.g., error information,power information, network, connection information, etc.). In theexample shown in FIG. 49, five indicators 3066 are provided on thefascia 3061. In other implementations, however, greater or fewerindicators 3066 may be provided.

In accordance with some aspects, the chassis 3010 includes a backplane3040 (e.g., see FIGS. 50, 77, and 91). The circuit board arrangement3120 of each blade 3100 positioned in the chassis 3010 connect to thebackplane 3040 of the chassis 3010. In some implementations, the blades3100 are connected to the backplane 3040 only when the blades 3100 arein the closed position relative to the chassis 3010. In otherimplementations, however, the blades 3100 are connected to the backplane3040 when the blade 3100 is in both the closed position and at least oneextended position as will be disclosed in more detail herein.

An example chassis backplane 3040 are shown in FIGS. 50, 77, and 91. Thechassis backplane 3040 includes one or more connector ports 3042 mountedto a circuit board 3041. For example, the backplane 3040 may include oneor more blade ports 3042, each of which is configured to receive aconnection end of the circuit board arrangement of a blade (e.g.,connection end 3125 of circuit board arrangement 3120 of blade 3100 ofFIGS. 55, 64, and 68). The backplane 3040 also may include a statusboard port 3046 configured to receive a connector or connection edge ofa status board (e.g., status board 3070 of FIG. 45). In someimplementations, the circuit board arrangements and/or the status boardshave card-edge connectors. In other implementations, the circuit boardarrangements and/or status boards can connect to the backplane 3040using a different type of electrical connector.

In some implementations, the status board 3070 includes a data port 3073(FIG. 45) at the front of the chassis 3010 that electrically connects amedia segment (e.g., a USB cable) inserted therein to the chassisbackplane 3040 via the printed circuit board of the status board 3070.Accordingly, a mobile device can access the chassis processor 3060and/or any of the blade processors 3140 from the front of the chassis3010. In certain implementations, sliding the status board 3070 at leastpartially out of the chassis 3010 disconnects the status board 3070 fromthe backplane 3040.

In some implementations, a cover 3050 may be positioned at the rear ofthe chassis 3010 to provide protection for media segments 3200 routed tothe rear of the chassis 3010. As shown in FIG. 46, the cover 3050includes sidewalls 3053 extending between a top 3051 and a bottom 3052.In certain implementations, vents may be provided in the top 3051 and/orthe bottom 3052 to inhibit overheating of the chassis processor 3060. Arear wall 3054 extends between the sidewalls 3053 and between the top3051 and bottom 3052. Cable tie locations may be provided on theexterior of the rear wall 3054 (see FIG. 48).

In certain implementations, the top 3051 and rear walls 3054 define acutout 3055 that accommodates the support structure 3020 of the chassis3010. The fascia 3063 of the chassis processor 3060 may be accessiblethrough the cutout 3055. The cover 3050 defines open portions 3056 atthe sides to facilitate routing of media segments 3200 to the rear ofthe chassis 3010. For example, the cable management structure 3030, 3035may be accessible through the open portions 3056 of the cover 3050. Inthe example shown, the open portion 3056 extends over only a portion ofeach side, top, and bottom of the cover 3050. In other implementations,one or both sides of the cover 3050 may be open in their entirety.

In some implementations, the cover 3050 includes tabs, slots, or otherattachment features that interact with tabs, slots, or other attachmentfeatures of the chassis 3010 to secure the cover 3050 to the chassis3010. In the example shown, the cover 3050 includes two forward tabs3057 and two sideways tabs 3058 that interact with tabs 3024 of thechassis 3010 to align the cover 3050 on the chassis 3010. In certainimplementations, the cover 3050 is secured to the chassis 3010 byfasteners 3059. For example, one or more fasteners 3059 may extendthrough the rear wall 3054 of the cover and through tabs 3029 (FIG. 47)extending outwardly from the support structure 3020 of the chassis 3010.

In the example shown in FIGS. 45-49, the chassis 3010 of panel system3000 is configured to receive about four blades 3100. For example, thechassis 3010 includes four guides 3015, each guide 3015 being configuredto receive one blade 3100. In other implementations, however, a chassismay be configured to receive greater or fewer blades 3100. For example,FIGS. 50-51 show one example panel system 3000′ that is configured toreceive eight blades 3100. The chassis 3010′ includes eight guides 3015on either side of the chassis 3010′. FIGS. 52-53 show another examplepanel system 3000″ that is configured to receive two blades 3100. Thechassis 3010″ includes two guides 3015″ on each side of the chassis3010″.

FIGS. 54-74 show various example blades 3100 configured to be mountedwithin any of the chasses 3010, 3010′, 3010″. For ease in understanding,however, this disclosure will show the blades interacting with chassis3010. In accordance with some aspects, different types of blades 3100may be mounted within the same chassis 3010 (see FIGS. 75 and 143). Inother implementations, however, blades 3100 of the same type may bemounted within the chassis 3010. The type of management structure (e.g.,management arrangements 3030, 3035) provided at the rear of the chassis3010 may depend on the type or types of blades 3100 mounted within thechassis 3010.

FIGS. 54-56 illustrate an example blades 3100 configured to mount in anyof the chassis 3010, 3010′, 3010″ disclosed above. In general, eachblade 3100 includes a generally planar base 3110 having a front, a rear,and opposing sides. A handle 3108 extends from the front of the base3110 to facilitate positioning of the blade 3100 relative to the chassis3010 as will be described in more detail herein. Outer extensions 3112extend from the rear of the base 3110. At least one of the outerextensions 3112 defines a notch 3105 in an external side (FIG. 54).Inner extensions 3113 also extend from the rear of the base 3110. In theexample shown, the base 3110 includes two spaced apart inner flanges3113. Each inner flange 3113 defines a tab (e.g., cable tie location)3114 at which media segments can be secured as will be described in moredetail herein.

Each blade 3100 also includes a coupler arrangement 3150. A frame 3115holds at least a portion of the coupler arrangement 3150 to the blade3100. In some implementations, the coupler arrangement defines one ormore rear ports at which incoming media segments are received and one ormore front ports at which outgoing media segments are received. As notedabove, the terms “incoming” and “outgoing” are used for convenience onlyand do not imply that communication signals flow in only one direction.In some implementations, the front and rear ports are defined bycouplers 3151 3153 located at the front of the blade 3100. In otherimplementations, the rear ports are defined by couplers 3155 located atthe rear of the blade 3100.

In some implementations, each coupler 3151, 3153, 3155 of the couplerarrangement 3150 is an adapter configured to receive and opticallycouple optical fiber cables. As the term is used herein, optical fibercables refer to one or more strands of optical fibers. In certainimplementations, the optical fibers are jacketed or buffered. In someimplementations, the optical fibers of a cable are individuallyconnectorized (e.g., with LC connectors, SC connectors, ST connectors,FC connectors, LX.5 connectors, etc.). In other implementations,multiple optical fibers may be terminated at the same connector (e.g.,an MPO connector).

In other implementations, one or more couplers 3151, 3153, 3155 of thecoupler arrangement 3150 is configured to electrically connect two ormore electrical media segments. For example, the coupler arrangement mayinclude a socket for receiving an electrical connector terminating aconductor cable. The socket may connect to one or more IDCs at whichother conductors are terminated. In other implementations, the couplerarrangement may include other types of terminations of electricalconductors. In still other implementations, the coupler arrangement mayinclude media converters that are configured to receive one or moreoptical fiber and one or more electrical conductors to create acommunications pathway therebetween.

In some implementations, the blade 3100 is a smart blade as described inmore detail herein with reference to FIGS. 128-130. The couplerarrangement 3150 of the smart blade 3100 also includes one or more mediareading interfaces that are configured to read physical layerinformation stored on or in the media segments 3200 received at thecoupler arrangement 3150. In certain implementations, each couplerarrangement includes at least one media reading interface. Indeed, insome implementations, each front port of the coupler arrangementincludes a media reading interface. In other implementations, adjacentpairs of front ports each include a media reading interface. In stillother implementations, one or more rear ports also may include mediareading interfaces. Example media reading interfaces are disclosed inU.S. Provisional Application Nos. 61/303,961; 61/413,828; 61/437,504;and U.S. Pat. No. 8,690,593 incorporated by reference above.

In some implementations, an example smart blade 3100 includes a circuitboard arrangement 3120 and a blade processor 3140. The circuit boardarrangement 3120 connects the blade processor 3140 to the media readinginterfaces of the coupler arrangement 3150. In some implementations, theblade processor 3140 does not modify or otherwise interfere withcommunications signals (e.g., signals 51 of FIG. 1) propagating overmedia segments plugged into ports of the coupler arrangement 3150. Incertain implementations, the blade processor 3140 does not monitor suchcommunications signals. In certain implementations, the blade processor3140 is isolated from such communications signals.

A first portion of the circuit board arrangement 3120 extends across thefront of the blade 3100. The front couplers 3151, 3153 (FIGS. 57, 65,and 70) are coupled to the first portion of the circuit boardarrangement 3120. The second portion of the circuit board arrangement3120 extends rearwardly from the first portion. In some implementations,the second portion of the circuit board arrangement 3120 is sufficientlynarrow to fit between the intermediate flanges 3113 of the blade base3110. In some implementations, the circuit board arrangement 3120includes a single printed circuit board.

In other implementations, however, the circuit board arrangement 3120includes multiple circuit boards that are electrically connectedtogether. In certain implementations, the circuit board arrangement 3120includes a first circuit board 3122 and a second circuit board 3124. Inone implementation, the first circuit board 3122 defines at least thefirst portion of the circuit board arrangement 3120 and the secondcircuit board 3124 defines at least part of the second portion of thecircuit board arrangement 3120. In certain implementations, the firstand second boards 3122, 3124 are configured to move relative to eachother as will be described in more detail herein.

In certain implementations, the mounting frame 3115 is interrupted(e.g., defines a reduced height) at an intermediate section of the frame3115, thereby defining a gap between two adjacent groups of couplers3151. The blade processor 3140 is mounted to the first portion of thecircuit board arrangement 3120 at the interrupted section of the frame3115 (see FIG. 57). In one implementation, the processor 3140 is mountedto the circuit board arrangement 3120 via s SIM-card type connector. Inother implementations, however, the processor 3140 may be otherwiseconnected to the circuit board arrangement 3120 (e.g., mezzanineconnectors).

In some implementations, the blade 3100 may have an open top. In suchimplementations, the rear ports of the couplers 3151 may be accessiblethrough the open top of the blade 3100. Accordingly, the connectorizedends of the incoming media segments 3210 may be accessible through theopen top of the blade 3100. The processor 3140 also may be accessiblethrough the open top of the blade 3100. The interrupted top portion 3116of the frame 3115 enhances access to the blade processor 3140 throughthe open top.

In certain implementations, the blade base 3110 defines one or moreopenings 3109 (FIGS. 57 and 62) at the rear of the front couplers 3151.In some implementations, the first portion of the circuit boardarrangement 3120 does not extend rearwardly of the front couplers 3151.Accordingly, the openings 3109 provide finger access to the rear portsof the couplers 3151 from a bottom of the blade 3100. In the exampleshown, the base 3110 defines one opening 3109 on either side of theprocessor 3140.

In some implementations, one or more retention fingers 3160 are mountedto the front of the blade 3100 to manage and/or organize the outgoingmedia segments 3220. FIG. 56 illustrates one example retention finger3160 configured to facilitate fiber cable management. In certainimplementations, the cable retention fingers 3160 may be installed onthe mounting frame 3115. For example, each cable retention finger 3160includes a base 3161 that may be fastened or otherwise attached to aportion (e.g., bracket 3117) of the frame 3115. In otherimplementations, the base 3161 of each retention finger 3160 may attachto the base 3110 or cover 3103 of a blade 3100.

Bottom and top arms 3162, 3164, respectively, of each finger 3160 extendoutwardly from the base 3161 to an end 3167. The arms 3162, 3164, base3161, and end 3167 define an opening 3166 through which one or moremedia segments (e.g., optical fiber cables) can be routed. In theexample shown, the top arm 3164 defines a break 3165 through which mediasegments can pass into the opening 3166 without routing an end (e.g., anend terminated by a connector) of the media segment between the arms3162, 3164. In other implementations, the break 3165 may be provided inthe end 3167 or bottom 3164. A support flange 3163 extends between thebottom and top arms 3162, 3164 adjacent the base 3161. The supportflange 3163 inhibits the media segments retained within the opening 3166from being bent too far.

FIGS. 57-62 show a first example blade 3100A including a mounting frame3115A at which the front ports of a first example coupler arrangement3150A are positioned. The first example coupler arrangement 3150A (FIG.57) defines the front and rear ports of the blade 3100A. In someimplementations, the mounting frame 3115A holds at least part of thecoupler arrangement 3150A to the blade base 3110. For example, in someimplementations, the coupler arrangement 3150A includes a firstplurality of couplers 3151 held within the front openings of themounting frame 3115A.

The mounting frame 3115A generally includes a top 3116 connected to thebase 3110 by two or more brackets 3117 to define a generally open front.Additional brackets 3117 may extend between the top 3116 and base 3110to separate the front opening into multiple openings. In certainimplementations, the mounting frame 3115A includes tabs 3118 and flanges3119 that extend partially into the frame openings. The tabs 3118 andflanges 3119 aid in holding the couplers 3151. In the example shown, themounting frame 3115A defines four openings. In other implementations,however, the mounting frame 3115A may form greater or fewer openings. Insome implementations, the mounting frame 3115A is integral with the base3110. For example, the frame 3115A may be formed by bending a frontportion of the base 3110. In other implementations, however, the frame3115A can be a separate piece that is assembled to the base 3110.

In some implementations, multiple couplers 3151 are mounted within eachframe opening. In other implementations, however, a single coupler 3151may be mounted within each frame opening. In the example shown, threecouplers 3151 are mounted within each opening in the frame 3115A. Thecouplers 3151 have front ports that define the front ports of the blade3100A that are configured to receive the outgoing media segments 3210(e.g., see FIGS. 61-62). In some implementations, the couplers 3151 ofthe first coupler arrangement 3150A also define the rear ports of theblade 3100A that are configured to receive the incoming media segments3210 (e.g., see FIGS. 61-62). For example, in certain implementations,each coupler 3151 defines one or more through-openings 3159 (FIG. 60)extending between the front and rear ports. In other implementations,the first coupler arrangement 3150A includes additional couplers thatdefine the rear ports of the blade 3100A (e.g., see blade 3100C of FIGS.67-71).

In the example shown, each coupler 3151 includes four through-openings3159, thereby providing a total of forty-eight through-openings 3159 onthe blade 3100A. Accordingly, the first example blade 3100A isconfigured to connect forty-eight pairs of media segments 3200. In otherimplementations, however, the blade 3100 may include greater or fewercouplers 3151 and each coupler 3151 may include greater or fewerthrough-openings. For example, each coupler 3151 may include one, two,eight, ten, or twelve through-openings 3159. In accordance with otheraspects, each coupler 3151 may define an unequal number of front andrear ports.

In some implementations, the couplers 3151 include fiber optic adaptersconfigured to receive one or more pairs of connectorized fiber cables(e.g., two LC-connector terminated cables, two SC-connector terminatedcables, two ST-connector terminated cables, two MPO-connector terminatedcables, etc.). In the example shown in FIG. 60, the couplers 3151 arequadruplex fiber optic adapters 3151 that optically couple together fourpairs of LC connectors. In other implementations, however, the couplers3151 can include monoplex fiber optic adapters, duplex fiber opticadapters, or other types of adapters. In still other implementations,the couplers 3151 may include one or more electrical sockets.

In certain implementations, dust caps 3152 can be provided in the portsof one or more of the through-openings 3159 of the adapters 3151. In theexample shown, each dust cap 3152 is configured to plug into twoadjacent ports of an adapter 3151 (e.g., see FIG. 60). In anotherimplementation, however, each dust caps 3152 may be configured to pluginto a single port of an adapter 3151. In other implementations, eachdust cap 3152 may be configured to plug into three or more ports of anadapter 3151.

As shown in FIGS. 57 and 60, the couplers 3151 are mounted to a circuitboard arrangement 3120A. In the example shown, the circuit boardarrangement 3120A is generally T-shaped. A first portion of the circuitboard arrangement 3120A extends across the front of the base 3110 and asecond portion of the circuit board arrangement 3120A extends to a rearof the base 3110. The first plurality of couplers 3151 are mounted ontop of the first portion of the circuit board arrangement 3120A.

For example, in FIG. 57, a row of spaced groups of the couplers 3151 aremounted to the first portion of the circuit board arrangement 3120A. Insome implementations, the couplers 3151 within each group are positioneddirectly next to each other (see FIG. 57). In other implementations, thecouplers 3151 within each group are spaced from each other. In theexample shown, each group of couplers 3151 is positioned to align withone of the openings of the frame 3115A. Accordingly, the front ports ofeach coupler 3151 are accessible through the front openings of the frame3115A at the front of the blade 3100A.

In certain implementations, the first example blade 3100A includes oneor more visual indicators 3128 to indicate status information of theblade 3100A (e.g., see FIGS. 57-59). For example, the visual indicators3128 may be used to indicate a coupler port, a set of coupler ports, acoupler 3151, or the first blade 3100A, itself. In one implementation,the first example blade 3100A includes a visual indicator 3128positioned adjacent each front port (e.g., FIG. 59). In anotherimplementation, the first example blade 3100A includes a visualindicator 3128 positioned adjacent each pair of front ports. In stillother implementations, the first example blade 3100A includes a singlevisual indicator 3128 per blade.

In one example implementation, the visual indicators 3128 include lightemitting diodes (LEDs). In accordance with some aspects, the bladeprocessor 3140 can indicate a particular coupler port (e.g., to show atechnician which port should receive a plug) by applying power to lightthe corresponding LED 3128. In accordance with other aspects, theprocessor 3140 can apply power to an LED 3128 to indicate a status ofthe corresponding port, set of ports, or blade. For example, theprocessor 3140 may apply power to the LED 3128 when a plug has beenreceived at a respective port.

In accordance with certain aspects, the processor 3140 can sendinstructions to the LED 3128 to display a particular color. For example,the processor 3140 may cause an LED 3128 to display a first color (e.g.,green) when a plug is inserted and physical layer information issuccessfully read, a second color (e.g., amber) when a plug is insertedand physical layer is not successfully read, and a third color (e.g.,red) when a plug is partially (or otherwise improperly) inserted intothe port. In other implementations, however, the LEDs 3128 can displaygreater or fewer colors or can indicate other types of statuses orerrors. In other implementations, however, other types of visualindicators may be used (e.g., an LCD screen, a touch screen a monitor,etc.).

FIGS. 61-62 show one example routing path for incoming and outgoingmedia segments 3210, 3220 on the first example blade 3100A. Outgoingmedia segments 3220 are routed to the couplers 3151 at the front of theblade 3100A. Connectorized ends 3222 of the outgoing media segments 3220are plugged into the front ports of the couplers 3151. For example, theconnectorized ends 3222 may be inserted through the openings of theframe 3115A and into the front port of the through-openings 3159 definedby the couplers 3151. The media segments 3220 may be managed by one ormore of the retention fingers 3160 coupled to the blade 3100A.

At least a first group of one or more incoming media segments 3210 arerouted to one of the intermediate flanges 3113. The incoming mediasegments 3210 of the first group are secured to the blade 3100A at theintermediate flange 3113. For example, the first media segments of thefirst group may be secured to the tab 3114 at the flange 3113 using acable tie 3039 (e.g., see FIGS. 77-79). For example, the cable tie 3039may be wrapped around the media segments 3200 and looped through the tab3114. Connectorized ends 3212 of the media segments 3210 are routed overthe base 3110 towards the front of the blade 3100A and plugged into therear ports of the couplers 3151.

FIGS. 63-66 show various views of a second example blade 3100B. Thesecond example blade 3100B includes a generally planar base 3110, ahandle 3108, outer extensions 3112, and inner extensions 3113. At leastone of the outer extensions 3112 defines a notch 3105 in an externalside. One or more tabs 3114 are provided at each inner flange 3113 toaid in securing a group of optical fibers to the blade 3100B. Retentionfingers 3160 may extend forwardly of the blade 3100B to aid in managingoutgoing media segments 3220.

The second example blade 3100B includes a second example couplerarrangement 3150B configured to connect incoming and outgoing fibersterminated with WO-connectors. The second coupler arrangement 3150Bincludes a row of couplers 3153 (FIG. 66) at the front of the blade3100B. In the example shown, the couplers 3153 are fiber optic adaptersconfigured to receive MPO-type fiber optic connectors. For example, inone implementation, each adapter 3153 is configured to optically coupletogether a pair of MPO-connectors. In other implementations, eachadapter 3153 may coupler together multiple pairs of MPO-connectors. Inthe example shown, dust plugs 3154 are mounted in front and rear portsof the adapters 3153.

In certain implementations, the second example blade 3100B includes acircuit board arrangement 3120B that includes multiple circuit boards.For example, in FIGS. 65 and 66, the circuit board arrangement 3100Bincludes a first circuit board 3122, a second circuit board 3124, and athird circuit board 3126. A processor 3140 connects to the first circuitboard 3122. The MPO adapters 3153 are sandwiched between the firstcircuit board 3122 and the third circuit board 3126. Accordingly, eachof the adapters 3153 may include a first media reading interface thatcommunicates with the processor 3140 through the first circuit board3122 and a second media reading interface 3157 that communicates withthe processor 3140 through the third circuit board 3126 (see FIG. 66).

The third circuit board 3126 is communicatively (e.g., electrically)connected to the first circuit board 3122. For example, in someimplementations, the third circuit board 3126 is connected to the firstcircuit board 3122 using pins 3129, which can be guided in a housing3128 positioned on the first circuit board 3122 (e.g., see FIG. 66).Accordingly, the first circuit board 3122 connects the processor 3140 tothe third circuit board 3126. In some implementations, the circuit boardarrangement 3120B includes multiple third circuit boards 3126. Forexample, in the implementation shown in FIG. 65, the circuit boardarrangement 3120B includes one third circuit board 3126 positioned overthe couplers 3153 on a first side of the processor 3140 and anotherthird circuit board 3126 positioned over the couplers 3153 on a secondside of the processor 3140.

The second example blade 3100B includes a second example mounting frame3115B coupling the second coupler arrangement 3150B to the base 3110(see FIGS. 65-66). The mounting frame 3115B is configured to hold thecouplers 3153 at the front of the blade 3100B while allowing access tothe front and rear ports of the couplers 3153. The mounting frame 3115Bincludes a fascia 3091 extending upwardly from the base 3110 (FIG. 66).The fascia 3091 defines one or more openings 3092 through which thefront ports of the couplers 3153 may be accessed. In the example shown,the mounting frame 3115B defines four openings. In otherimplementations, however, the mounting frame 3115B may form greater orfewer openings.

Tabs 3093 extend from the base 3110 of the blade 3100B and into theopenings 3092 to aid in retaining the couplers 3153. In someimplementations, the frame 3115B includes a tab 3093 for each coupler3153. In other implementations, the tabs 3093 extend between adjacentcouplers 3153 (see FIG. 63). In the example shown, four couplers 3153are mounted at each opening 3092. In other implementations, however,greater or fewer couplers 3153 can be mounted at each opening 3092. Insome implementations, the couplers 3153 of each opening are positioneddirectly next to each other. In other implementations, adjacent couplers3153 are spaced from each other.

A top member 3095, which extends generally perpendicular to the base3110, can be removeably connected to the fascia 3091 (see FIG. 66). Forexample, the top member 3095 can include brackets 3096 that defineopenings 3097 and the fascia 3091 may define openings 3094. Fastenerscan be inserted through the openings 3094, 3097 to connect the topmember 3095 to the fascia 3091. In certain implementations, the topmember 3095 may include a series of openings 3098. In the example shown,the openings 3098 accommodate fasteners holding the third circuit board3126 to the couplers 3153.

A finishing member 3099 (FIG. 65) can be mounted to the frame 3115B. Thefinishing member 3099 defines a curved surface that extends over alength of the openings 3092 defined in the fascia 3091. In someimplementations, the finishing member 3099 is configured to be held tothe frame 3115B using the retention fingers 3160 (discussed above withreference to FIG. 60). For example, the finishing members 3099 mayinclude hooked or bent ends that are held between the retention fingers3160 and the frame fascia 3091 (see FIG. 65).

In certain implementations, each coupler 3153 defines one or morethrough-openings 3159 (FIG. 66) extending between front and rear portsof the coupler 3153. In the example shown, each coupler 3153 includes asingle through-opening 3159, thereby providing a total of sixteenthrough-openings 3159 on the second example blade 3100B. Accordingly,the second blade 3100B is configured to connect sixteen pairs ofmulti-fiber cables 3200. In other implementations, however, the secondexample blade 3100B may include greater or fewer couplers 3153 and eachcoupler 3153 may include greater or fewer through-openings 3159. Inaccordance with other aspects, the couplers 3153 may define an unequalnumber of front and rear ports.

FIGS. 67-71 show different views of a third example blade 3100C. Thethird example blade 3100C includes a generally planar base 3110C (FIGS.70-71) that is substantially similar to the base 3110 of the firstexample blade 3100A. However, the base 3110C of the third blade 3100Cincludes brackets 3102 (FIG. 70). The base 3110C of the third blade3100C also includes a handle 3108, side flanges 3112, and inner flanges3113. At least one of the side flanges 3112 defines a notch 3105 in anexternal side. One or more tabs 3114 are provided at each inner flange3113 to aid in securing a group of optical fibers to the blade 3100C.

A cover arrangement 3103 (FIG. 67) may be mounted to the base 3110C atbrackets 3102. The cover arrangement 3103 includes one or more coversthat extend over the top of the blade 3100 between the frame 3115C and arear of the base 3110C. In one implementation, a single cover 3103extends over the entire blade 3100C. In other implementations, however,multiple covers 3103 can be installed on the blade 3100C. Each covercooperates with the base 3110 to define a blade interior 3111. In someimplementations, each cover 3103 includes side and/or rear walls thatextend down to the base 3110 (see FIG. 68). In other implementations,however, each cover 3103 is mounted to a separate rear wall and/or toseparate side walls of the blade 3100C. In still other implementations,each cover 3103 may be mounted to the frame 3115C. In the example shown,the outer and inner flanges 3112, 3113 extend outwardly from the coverarrangement 3103. In other implementations, however, the coverarrangement 3103 may extend over the outer and inner flanges 3112, 3113.

The third example blade 3100C also includes a third example couplerarrangement 3150C that is configured to connect incoming media segments3210 and outgoing media segments 3220. In the example shown, theincoming media segments 3210 are optical fibers terminated with MPO-typeconnectors and the outgoing media segments 3200 are optical fibersterminated with LC-type connectors. The coupler arrangement 3150Cincludes a first set of couplers 3151 defining the front ports of theblade 3100C and a second set of couplers 3155 defining the rear ports ofthe blade 3100C. In the example shown, the blade 3100C includes a leftcoupler region at which a plurality of the fiber optic adapters 3151 islocated, an intermediate region at which a blade processor 3140 islocated, and a right coupler region at which another plurality of thefiber optic adapters 3151 is located. A cover is installed over eachcoupler region. In accordance with some aspects, the intermediate regionof the blade 3100 is uncovered. Accordingly, the cover arrangement 3103does not inhibit access to the blade processor 3140.

The third blade 3100C also includes a mounting frame 3115C that aids inholding the first set of couplers 3151 to the base 3110C. In the exampleshown, the mounting frame 3115C is substantially the same as themounting frame 3115A of the first blade 3100A. Retention fingers 3160may be coupled to the frame 3115C to aid in managing outgoing mediasegments 3220. In some implementations, the top 3116 of the mountingframe 3115A is about flush with the cover arrangement 3103. In otherimplementations, the cover arrangement 3103 encompasses part of theframe 3115A. In other implementations, the top 3116 of the frame 3115Aextends over a portion of the cover arrangement 3103. In still otherimplementations, however, the third blade 3100C may include a frame3115C with a different configuration than frame 3115A.

In the example shown in FIGS. 69-71, the front couplers 3151 definethrough-openings that are configured to optically couple optical fibersterminated with LC connectors to optical fibers terminated with LCconnectors and the rear couplers 3155 are configured to optically coupleoptical cables terminated with MPO connectors to optical cablesterminated with MPO connectors. In other implementations, however, eachfront and rear couplers 3151, 3155 can be configured to couple togetherother types of media segments. In certain implementations, dust plugs3152 (FIG. 67) are mounted in front and rear sides of the front couplers3151 and dust plugs 3156 (FIG. 68) are mounted to the rear couplers3155.

The third blade 3100C also includes a third circuit board arrangement3120C having a first portion extending across the front of the base3110C and a second portion of the circuit board arrangement extending toa rear of the base 3110C. In certain implementations, the third circuitboard arrangement 3120C also includes a third portion that extends atlast partially along a rear side of the blade base 3110C (see FIGS.69-71). The first plurality of couplers 3151 are mounted on top of thefirst portion of the circuit board arrangement 3120C and the secondcouplers 3155 are mounted on top of the third portion of the circuitboard arrangement 3120C.

One or more connecting media segments 3230 connect the front couplers3151 to the rear couplers 3155. In accordance with some aspects, theconnecting media segments 3230 extend through the blade interior 3113defined between the base 3110 and the cover arrangement 3103. The coverarrangement 3103 inhibits access to and/or provides protection for theconnecting media segments 3230. The cover arrangement 3103 also mayinhibit access to and/or provides protection for the rear ports of thefirst set of couplers 3151 and/or the front ports of the second set ofcouplers 3155.

In the example shown, the connecting media segment 3230 includes a hydracable that includes a multi-fiber cable 3233 terminated at a multi-fiberconnector (e.g., an MPO connector) 3231 (FIGS. 69-71). Certain types ofhydra cable 3230 also includes one or more fanouts 3235 at which thefibers of the multi-fiber cable 3233 are separated into individualoptical fibers 3237. Each of the individual fibers 3237 is terminated ata fiber optic connector (e.g., an LC connector, an SC connector, an FCconnector, an ST connector, an LX.5 connector, etc.) 3239. Other typesof hydra cables 3230 may include a cable breakout as part of an MPO bootinstead of a separate fanout.

In some implementations, the hydra cable 3230 can be secured to the base3110 of the blade 3100C. For example, the fanout arrangement 3235 of thehydra cable 3230 can be secured to a raised tab 3104 (FIG. 91)positioned on the base 3110. In the example shown, a tie (e.g., a cabletie, a zip tie, etc.) 3232 is looped through the raised tab 3104 andwrapped around the fanout arrangement 3235 (see FIGS. 69-71). In otherimplementations, the tie 3232 may wrap around any portion of the hydracable 3230. In still other implementations, the fanout arrangement 3235may include a clip that allows the fanout arrangement 3235 to bedirectly attached to the raised tab 3104. In still otherimplementations, other types of connecting media segments 3230 mayoptically couple the front ports of the blade 3100C to the rear ports ofthe blade 3100C.

As shown in FIGS. 72-74, one or more labeling panels 3180 may beinstalled on the blades 3100 (e.g., blade 3100A, blade 3100B, and blade3100C) to provide labeling of the front coupler ports. Each labelingpanel 3180 extends across one or more front ports of the blade 3100.Labels (e.g., displaying numbers, letters, graphics, names, etc.) forthe front ports may be provided on the labeling panel 3180. For example,a printed label may be removably mounted to the labeling panel 3180.

Each of the labeling panels 3180 may be configured to connect to one ormore of the retention fingers 3160 extending forwardly of the blade3100. In the example shown, each labeling panel 3180 extends betweendistal ends 3167 of two adjacent retention fingers 3160. In certainimplementations, the retention fingers 3160 are sufficiently long that agap defined between the front ports and each labeling panel 3180 allowseach optical fiber plugged into one of the front ports a sufficient bendradius between the front port and the through-opening 3166 of theretention finger 3160 (e.g., see FIGS. 70 and 71).

One example labeling panel 3180 may be found in FIG. 74. The labelingpanel 3180 includes a generally planar labeling surface 3181 on which alabel may be provided. For example, in one implementation, a label maybe affixed to the labeling surface 3181. In other implementations, thelabeling panel 3180 also includes tabs 3182 at the top and/or bottom ofthe panel 3180 and nubs 3183 at opposing sides of the panel 3180 to aidin retaining one or more labels. In the example shown, the labelingpanel 3180 includes one nub 3183 at each side of the labeling surface3183, two tabs 3182 at the top of the labeling surface 3181 intermediatethe two nubs 3183, and two tabs 3182 at the bottom of the labelingsurface 3181 intermediate the two nubs 3183.

The labeling panel 3180 includes one or more attachment members 3184configured to secure the labeling panel 3180 to the ends 3167 of theretention fingers 3160. In some implementations, the attachment members3184 include grip fingers configured to snap to the distal ends 3167 ofthe retention fingers 3160. In the example shown, each labeling panel3180 includes top and bottom grip fingers 3184 at each side of the panel3180. In some implementations, the end 3167 of each retention finger3160 includes at least one vertically extending mounting pin 3168. Insome such implementations, the grip fingers 3184 of the labeling panel3180 snap-fits or otherwise attaches to the mounting pins 3168.

In certain implementations, the end 3167 of each finger 3160 includestwo spaced mounting pins 3168 (e.g., see FIG. 56). Accordingly, eachretention fingers 3160 is configured to receive and support two adjacentlabeling panels 3180 (e.g., see FIG. 72). In some implementations, eachmounting pin 3168 defines one or more reduced diameter sections 3169.For example, in the implementation shown in FIG. 56, the ends of eachpin 3168 define reduced diameter sections 3169. In some implementations,the grip fingers 3184 are sized to snap-fit to the reduced diametersections 3169 of the mounting pins 3168. In other implementations, thegrip fingers 3184 are configured to snap-fit to mounting pins 3168 atany point along the length.

In one implementation, the labeling panel 3180 has a height that allowsboth the top and bottom grip fingers 3184 at each side of the panel 3180to attach to the same retention finger 3160. In other implementations,the labeling panel 3180 is sufficiently tall to provide labeling for thefront ports on two or more blades 3100. For example, the labeling panel3180 may be sufficiently tall to extend across the front ports ofmultiple (e.g., two, three, four, eight, etc.) blades 3100. In suchimplementations, the top grip fingers 3184 may attach to the retentionfingers 3160 extending from a first blade 3100 and the bottom gripfingers 3184 may attach to the retention fingers 3160 extending from asecond blade 3100.

In certain implementations, the grip fingers 3184 are configured torotate about the mounting pins 3168. Rotating the labeling panels 3180about one of the mounting pins 3168 may facilitate accessing the frontports of the blade 3100 that are located behind the labeling panel 3180.In some implementations, the labeling panels 3180 can be rotated bydetaching one side of the labeling panel 3180 from one of the mountingpins 3168. For example, in FIG. 73, the attachment members 3184 on oneside of the bottom, left labeling panel 3180 have been disengaged froman example mounting pin 3168 to allow the labeling panel 3180 to rotateoutwardly about another mounting pin 3168 at the opposite side of thelabeling panel 3180. In certain implementations, the labeling panels3180 also may be fully detached from the retention fingers 3160.

FIGS. 75 and 76 illustrate one example bladed panel system 3000 in whicha plurality of blades 3100 is mounted within an example chassis 3010. Inthe example shown, the plurality of blades 3100 includes each type ofblade 3100A, 3100B, 3100C disclosed above. In particular, the upperblade is configured the same as the second example blade 3100B disclosedabove with reference to FIGS. 63-66; the middle blade is configured thesame as the first example blade 3100A disclosed above with reference toFIGS. 57-62; and the lower blade is configured the same as the thirdexample blade 3100C disclosed above with reference to FIGS. 67-71.Accordingly, the upper blade is configured to receive incoming andoutgoing media segments 3210, 3220 terminated with MPO connectors. Themiddle blade 3100A is configured to receive incoming and outgoing mediasegments 3210, 3220 terminated with LC connectors. The lower blade 3100Cis configured to receive incoming media segments 3210 terminated withMPO connectors and outgoing media segments 3220 terminated with LCconnectors.

In accordance with some aspects, the bladed panel system 3000 isconfigured to enable the blades 3100 to move relative to the chassis3010 into one or more positions. Moving one of the blades 3100 to adifferent position relative to the other blades 3100 in the chassis 3010may aid a user in accessing the coupler ports of the blade 3100 and/orany media segments inserted therein. For example, moving one of theblades 3100 forward of the other blades 3100 may provide space for auser to grasp a connector inserted into one of the coupler ports of theblade 3100. In accordance with certain aspects, moving one of the blades3100 to a different position also may provide access to the bladeprocessor 3140.

In some implementations, each blade 3100 may move between a closedposition and a first extended position. In the closed position, theblade 3100 is positioned within the chassis so that the front ports ofthe blade 3100 are located at the open front of the chassis 3010 and theretention fingers extend forwardly of the chassis 3010. In the firstextended position, at least the front ports of the blade 3100 arelocated forwardly of the open front of the chassis 3010. In certainimplementations, the rear ports of the front couplers 3151 also arelocated forwardly of the open front of the chassis 3010 when the blade3100 is in the first extended position.

In some implementations, the blades 3100 also may move to a secondextended position. In the second extended position, the front ports ofthe blade 3100 are located farther forward of the front chassis openingcompared to their location in the first extended position. In someimplementations, the blade processor 3140 is accessible when the blade3100 is in the second extended position. In certain implementations, theblade processor 3140 is accessible when the blade 3100 is in the firstextended position. In certain implementations, each of the blades 3100may be latched or otherwise releasably secured into at least one of thepositions as will be discussed in more detail with respect to FIGS.91-127.

By way of example, in FIGS. 75 and 76, the upper blade 3100B is in aclosed position; the middle blade 3100A is in a first extended position,and the lower blade 3100C is in a second extended position. The frontports of the upper blade 3100B generally align with the open front ofthe chassis housing 3010. The rear ports of the front couplers 3153 andthe processor 3140 of the upper blade 3100B are not accessible. Thefront ports of the middle blade 3100A are spaced forward of the openfront of the chassis 3010. The rear ports of the front couplers 3151and/or the processor 3140 may be accessible from the front of thechassis 3010. The front ports of the lower blade 3100C are spacedfarther forward of the open front of the chassis 3010 than the frontports of the middle blade 3100A. A cover arrangement 3103 blocks accessfrom the front of the chassis 3010 to the rear ports of the frontcouplers 3151 of the lower blade 3100C.

The bladed panel system 3000 is configured to enable the blades 3100 tomove (e.g., slide) relative to the chassis 3010 (e.g., see FIGS. 47 and48). In certain implementations, the blades 3100 are configured totravel along the direction of the connector insertion axis A_(I) (FIG.91). For example, the blades 3100 may travel forwardly and rearwardlyrelative to the chassis 3010. In some implementations, each blade 3100is configured to travel over a distance ranging from about one inch toabout five inches between the closed position and the first extendedposition. Indeed, in some implementations, each blade 3100 travels overa distance ranging from about two inches to about four inches betweenthe closed position and the first extended position. In one exampleimplementation, each blade 3100 travels about three inches between theclosed position and the first extended position.

In some implementations, each blade 3100 travels over a distance rangingfrom about four inches to about eight inches between the closed positionand the second extended position. Indeed, in some implementations, eachblade 3100 travels over a distance ranging from about five inches toabout seven inches between the closed position and the second extendedposition. In one example implementation, each blade 3100 travels aboutsix inches between the closed position and the second extended position.In some implementations, each blade 3100 travels about three inchesbetween the first and second extended positions. In otherimplementations, however, each blade 3100 may travel a greater or lesseramount between the first and second extended positions (e.g., one inch,two inches, three inches, four inches, etc.).

Referring to FIGS. 77-90, management structures at the front and rear ofthe chassis 3010, blades 3100, and frames (e.g., racks, cabinets, etc.)secure the incoming media segments 3210 and outgoing media segments 3220to the chassis 3010 while accommodating movement of the blades 3100relative to the chassis 3010. For example, the incoming cables 3210 maybe routed to the rear of the chassis 3010 so as to provide a slacklength 3215 of the incoming media segments 3210 (see FIG. 78). In someimplementations, the incoming media segments 3210 may include a curvedslack length segment 3215 between the management structures (e.g.,clamps 3030, fanouts 3035, etc.) at the rear of the chassis 3010 and themanagement structures (e.g., cable ties 3039) at the rear of the blade3100.

The slack length 3215 enables the connectorized ends 3212 of the mediasegments 3210 to remain plugged into the blade couplers (e.g., rearcouplers 3155) when the blade 3100 is moved to an extended position. Forexample, in some implementations, the curved slack length may straightenas the blades 3100 are moved forward of the chassis 3010. In certainimplementations, the management structures (e.g., cable ties 3039) onthe blade 3100 secure the media segments 3210 to the blade 3100 whileallowing for movement of the media segments 3210 relative to the blade3100 to accommodate movement of the blades 3100 relative to the chassis3010. For example, the slack length 3215 can slide through the cableties 3039 as the blades 3100 are moved forward and rearward of thechassis 3010.

In some implementations, the cable tie region is positioned so that theincoming media segments 3210 extend rearwardly from the chassismanagement structures to the cable ties 3039 when the blade 3100 is inthe closed position. In certain implementations, the cable tie region oneach inner extension 3113 is aligned with the chassis managementstructures when the blade 3100 is in the closed position. In someimplementations, the cable tie region is positioned so that the incomingmedia segments 3210 extend generally sideways or forwardly from thechassis management structures to the cable tie region 3039 when theblade 3100 is in the first extended position. In certainimplementations, the cable tie region on each inner extension 3113 isaligned with the backplane 2030 when the blade 3100 is in the firstextended position (FIG. 79).

The outgoing media segments 3220 plugged into the front ports of theblades 3100 may be secured to an equipment rack or other structure towhich the chassis 3010 mounted. Accordingly, movement of the blades 3100relative to the chassis 3010 moves the media segments 3220 relative tothe rack. The openings 3166 defined in the cable retention fingers 3160are sufficiently long to aid in accommodate movement of the outgoingmedia segments 3220 within the openings 3166 when the blades 3100 aremoved between closed and extended positions.

In accordance with some aspects, additional management structures alsomay be provided on the rack to accommodate movement of the blades. Forexample, FIGS. 80-90 illustrate an example bladed panel system in whichat least one chassis 3010 and at least one bracket 4300 are mounted to aframe 4400. The brackets 4300 are mounted at the chassis 3010 to aid inrouting the outgoing media segments 3220 from the front of the blades3100 to elsewhere on the frame 4400.

The chassis 3010 is configured to receive one or more blades 3100defining a plurality of front ports at which outgoing media segments3220 may be positioned. In the example shown, each blade 3100 alsoincludes multiple retention fingers 3160 FIG. 56) extending forwardly ofthe blade 3100 to manage the outgoing media segments 3220. Each of theblades 3100 is configured to move relative to the chassis 3010 between aclosed position and at least one extended position. In certainimplementations, each blade 3100 is configured to move between a closedposition, a first extended position, and a second extended position.

In some implementations, the brackets 4300 are mounted to the frame 4400through the mounting brackets of the chassis 3010. In otherimplementations, the brackets 4300 may be mounted directly to the frame4400 adjacent the chassis 3010. In the example shown, one bracket 4300is mounted at each side of the chassis 3010. In other implementations,however, greater or fewer brackets 4300 may be provided. For example, insome implementations, multiple brackets 4300 may be provided at eachside of a chassis 3010. In other implementations, a single bracket 4300may span multiple adjacent chasses 3010.

Each bracket 4300 is configured to manage (e.g., secure and/or organize)slack length of outgoing media segments 3220 routed to the front portsof the blades 3100. The slack length of the outgoing media segments 3220accommodates movement of the blades 3100 between the various positions.For example, compare the cable routing of FIGS. 80-82. In FIG. 80, oneexample blade 3100 is positioned within the chassis 3010 in the closedposition. Outgoing media segments 3220, which are plugged into the frontports of the blade 3100, are routed to a side of the chassis 3010. Slacklength of the outgoing media segments 3220 is routed around an examplebracket 4300 positioned at the side of the chassis 3010. The outgoingmedia segments 3220 may be secured to the side of the chassis 3010 or tothe frame 4400 after being routed around the bracket 4300.

In FIG. 81, the blade 3100 has been moved to the first extended positionrelative to the chassis 3010. The front ports of the blade 3100 arepositioned forwardly of the open front of the chassis 3010. The bracket4300 enables movement of the outgoing media segments 3220 plugged intothe blade front ports without pulling on the outgoing media segments3220 (e.g., at the point where the outgoing media segments 3220 secureto the chassis 3010 or frame 4400). For example, the outgoing mediasegments 3220 may unwrap/lift away from at least a portion of thebracket 4300. In certain implementations, the bracket 4300 continues tomanage (e.g., secure and/or organize) the slack length of the outgoingmedia segments 3220 while the blade 3100 is in the extended position.

In FIG. 82, the blade 3100 has been further moved to the second extendedposition relative to the chassis 3010. The front ports of the blade 3100are positioned farther forwardly of the chassis 3010 than in the firstextended position. The bracket 4300 enables the further movement of theoutgoing media segments 3220 plugged into the front ports withoutpulling on the outgoing media segments 3220 (e.g., at the point wherethe outgoing media segments 3220 secure to the chassis 3010 or frame4400). For example, the outgoing media segments 3220 may continue tounwrap/lift away from at least a portion of the bracket 4300. In certainimplementations, the outgoing media segments 3220 may be at leastpartially disconnected from the bracket 4300 when the blade 3100 ismoved to the second extended position.

FIGS. 83-89 show one example bracket 4300 configured to manage the slacklength of outgoing media segments 3220 plugged into the front ports ofthe blades 3100. The example bracket 4300 is suitable for use inmanaging the slack length of any media segments positioned at the frontof any blade disclosed herein. The bracket 4300 includes a mounting base4310 at which the bracket 4300 may be secured to the frame 4400 and/orto the chassis 3010. For example, the mounting base 4310 may define oneor more holes 4312 through which a fastener 4314 may extend to securethe base 4310 to the frame 4400 and/or chassis 3010.

A spacer flange 4320 extends forwardly of the mounting base 4310. Insome implementations, the spacer flange 4320 extends over a distancecomparable to the distance between the closed blade position and thefirst extended position. In some implementations, the spacer flange 4320extends forwardly less than about 4 inches. Indeed, in someimplementations, the spacer flange 4320 extends forwardly less thanabout 3 inches. In other implementations, the spacer flange 4320 extendsforwardly about 2 inches.

At least one bend radius limiter arrangement 4330 extends from thespacer flange 4320 opposite the mounting base 4310. In someimplementations, the bend radius limiter arrangement 4330 defines asingle arced surface. For example, the bend radius limiter arrangement4330 may define a half-spool. In other implementations, the bend radiuslimiter arrangement 4330 includes two or more bend radius limiters. Forexample, the bend radius limiter arrangement 4330 shown in FIG. 83includes a first bend radius limiter 4333 and a second bend radiuslimiter 4337 joined by a spacer 4335.

The convex surface of the bend radius limiter arrangement 4330 defines asurface over which the slack length of one or more outgoing mediasegments 3220 may be routed. The concave surface of the bend radiuslimiter arrangement 4330 defines a channel 4340 along which one or moreof the outgoing media segments 3220 can be routed along the frame 4400as will be described in more detail herein.

One or more cable retention fingers 4350 are mounted to the bracket 4300to aid in managing the outgoing media segments 3220 routed around thebracket 4300. In certain implementations, the cable retention fingers4350 are mounted to the bracket 4300 at the bend radius limiterarrangement 4330. For example, as shown in FIG. 83, the cable retentionfingers 4350 may be mounted to the spacer 4335 separating two of thebend radius limiters 4333, 4337. In some implementations, multiple cableretention fingers 4350 are positioned in a column between the bendradius limiters 4333, 4337.

Each cable retention finger 4350 is includes a body 4352 defining anopening 4354 that is configured to receive one or more outgoing mediasegments 3220. For example, in some implementations, each retentionfinger 4350 includes a closing member 4356 that is configured to provideaccess to the opening 4354 to enable routing of the outgoing mediasegments 3220 through the cable retention fingers 4350 without insertingthe ends of the outgoing media segments 3220 through the openings 4354.In one implementation, the closing member 4356 defines a living hingethat enables the closing member 4356 to move relative to the finger body4352. In other implementations, each finger 4350 defines an uncoveredslot through which the outgoing media segments 3220 may be inserted intoand removed from the finger 4350. In certain implementations, theclosing member 4356 may be opened to accommodate movement of the mediasegments 3220 when the blade 3100 is moved to the second extendedposition (see FIG. 82).

As best seen in FIG. 90, the bracket 4300 also may include a guidemember 4360 at an opposite side of the bend radius limiter arrangement4330 from the spacer flange 4320. The guide member 4360 guides theoutgoing media segments 3220 routed around the bend radius limiterarrangement 4330 to the channel 4340. In some implementations, the guide4360 includes a body 4362 that defines an opening 4365 through which oneor more of the outgoing media segments 3220 may be routed. In certainimplementations, the body 4362 of the guide 4360 defines a slot 4364 orother opening through which the outgoing media segments 3220 may beinserted into the opening 4365 without feeding the ends of the outgoingmedia segments 3220 through the guide member 4360.

One or more securement members 4370 may be provided to aid in routingthe outgoing media segments 3220 to the guide member 4360 and/or insecuring the outgoing media segments 3220 to the bracket 4300. In theexample shown in FIG. 90, the securement members 4370 include zip ties.In other implementations, however, other types of securement members(e.g., cable ties, twist ties, straps, hooks, etc.) may be provided.

Referring to FIGS. 91-127, in accordance with some aspects, each blade(e.g., any of blades 1100, 2100, 3100) may be secured into one or morepositions relative to the chassis. In accordance with some aspects, eachblade 3100 may be latched or otherwise secured in the closed position.For example, as shown in FIGS. 91-94, each blade 3100 may cooperate witha detent 3017 on the chassis housing 3013 to releasably lock the blade3100 in the closed position. Sufficient force to overcome the resistanceof the detent 3017 is applied to the blade 3100 to move the blade 3100to one of the extended positions (e.g., see FIG. 94). Sufficient forceto overcome the detent 3017 also is applied to lock the blade 3100 inthe closed position (e.g., see FIG. 92).

In some implementations, one or more detents 3017 may be provided at arear of the chassis housing 3013. For example, a column of detents 3017may be provided on (e.g., snapped into holes defined in) at least one ofthe chassis side walls 3011 at the rear of the chassis 3010 (see FIG.93). The notch 3105 defined in at least one of the side flanges 3112 ofeach blade 3100 cooperates with one of the detents 3017 to inhibitforward movement of the blade 3100. In the example shown, only one ofthe side flanges 3112 defines a notch 3105 (e.g., see FIGS. 54, 63, and67). In other implementations, however, the detents 3017 may be providedon both sides of the chassis housing 3013 and the notches 3105 may beprovided on both side flanges 3112.

In some implementations, the chassis housing 3013 may be configured toinhibit a blade 3100 from being moved too far rearward relative to thechassis 3010. For example, one or more stops 3018 may be provided on theside walls 3011 of the chassis housing 3013 (FIG. 92). In the exampleshown, the stops 3018 are positioned forwardly of the detents 3017. Inthe example shown in FIG. 92, the rearward shoulder 3175 of the secondlatching tab 3176 of a blade 3100 abuts against one of the stops 3018 toinhibit further rearward motion of the blade 3100.

In accordance with some aspects, each blade 3100 includes a latchingarrangement that is configured to secure the blade 3100 in one or morepositions. FIGS. 95-97 illustrate one example latching arrangement bywhich a blade 3100 may be latched or otherwise secured in the firstextended position. Each blade 3100 with the example latching arrangementincludes one or more latching tabs 3170 (FIGS. 55, 64, and 68)configured to engage with the chassis housing 3010 to lock the blade3100 in one of a plurality of positions.

In such implementations, at least one side of the chassis housing 3010defines one or more latching recesses 3009 or openings (FIGS. 91 and 95)that receive the latching tabs 3170. In certain implementations, bothsides of the blade 3100 may include one or more latching tabs 3170configured to cooperate with one or more latching openings 3009 definedin both sides of the chassis housing 3010. In some implementations, thechassis 3010 defines one latching opening 3009 for each blade 3100 atthe front of the chassis 3010. In other implementations, the chassis3010 defines a latching opening 3009 at the front of each side wall 3011for each blade 3100 to be received (e.g., see FIG. 101). In still otherimplementations, each side 3011 of the chassis 3010 may define multipleopenings 3009 for each blade 3100 (e.g., see FIG. 120).

Example blade latching tabs 3170 are shown in FIGS. 55, 63, and 68. Eachlatching tab 3170 includes a resilient body 3171 having a mounting end3172 and a free end. The mounting end 3172 of the tab body 3171 issecured to the blade base 3110 (e.g., via fasteners, welding, etc.). Thefree end of the body 3171 defines a latching surface 3173 having firstand second shoulders 3174, 3175, respectively (see FIGS. 54 and 55).When the blade 3100 is inserted into the chassis 3010, the firstshoulder 3174 faces the front of the chassis housing 3013 and the secondshoulder 3175 faces the rear of the chassis housing 3013 (see FIG. 98).

When a blade 3100 is located in the chassis 3010 in the closed position,the distal end of the first latching tab 3170 abuts against the sidewalls 3011 of the chassis housing 3013. When the blade 3100 is movedforwardly (e.g., by pulling handle 3108), the latching surface 3173 ofthe tab 3170 moves along the side wall 3011 until the latching surface3173 aligns with the latching recess 3009 of the chassis housing 3013.When aligned, the latching surface 3173 pops into the latching recess3009 (see FIG. 96). Front and rear shoulders 3174 and 3175 of thelatching tab 3170 abut against edges of the side wall 3011 to inhibitforward and rearward movement of the blade 3100 (see FIG. 96). Pushingthe latching surface 3173 sufficiently inwards for the shoulders 3174,3175 to clear the side wall edges releases the blade 3100, therebyenabling forward and rearward movement of the blade 3100 relative to thechassis 3010.

In accordance with some aspects, each blade 3100 also may be latched orotherwise secured in a second extended position. For example, in someimplementations, each blade 3100 may include at least a second latchingtab 3176 positioned further rearward on the blade 3100 than the firstlatching tab 3170 (see FIGS. 55, 63, and 68). In the example shown, thesecond latching tab 3176 is structured the same as the first latchingtab 3170. In other implementations, however, the second latching tab3176 may have a different structure. In some implementations, the secondlatching tab 3176 is configured to engage with the openings 3009 of thechassis housing 3013 to lock the blade 3100 in the second extendedposition (see FIG. 97). In other implementations, the second latchingtab 3176 interacts with a different set of latching recesses or openingsthan the first latching tab 3170.

In the example shown in FIGS. 75 and 76, the latching tabs 3170, 3176 ofthe upper blade 3100B are contained within the chassis housing 3013 and,accordingly, are not visible. No portion of the tabs 3170, 3176 isvisible through the chassis opening 3009. The first latching tab 3170Bof the middle blade 3100A is latched into one of the latching openings3009 of the chassis 3013. The second latching tab 3176 of the middleblade 3100A is contained within the housing 3013. The first latching tab3170C of the lower blade 3100C is external of the chassis housing 3013.The second latching tab 3176C of the lower blade 3100C is latched intoanother opening 3009 of the chassis housing 3013.

In accordance with some aspects, the blade 3100 can be completelyremoved from the chassis housing 3013. For example, to remove the blade3100 from the chassis housing 3010, a blade 3100 may first be moved tothe first extended position at which the first latching tab 3170 snapsinto the latching opening 3009 of the chassis housing 3013. Bydepressing the first latching tab 3170 free of the opening 3009, theblade 3100 may be moved further forward of the chassis 3010 to thesecond extended position. By depressing the second latching tab 3176 ofthe blade 3100 through the chassis opening 3009, the blade 3100 may bepulled still further forward of the chassis 3010 until the blade 3100 isfree of the chassis housing 3013.

FIGS. 99-127 show some alternative latching arrangements by which ablade may be secured in one or more positions relative to a chassis. Inaccordance with certain aspects, the latching arrangements areconfigured to be operated from the front of the chassis. In accordancewith certain aspects, each of the latching arrangements is configured tobe operated using one hand. In accordance with certain aspects, thelatching arrangements include actuation members that are positionedoutside of fiber routing paths. Indeed, in accordance with some aspects,the latching arrangements include actuators extending forwardly fromcentral sections of the chasses.

For ease in understanding, the various latching arrangements will beshown installed on blade 3100 described above. FIGS. 99-113 show oneexample latching arrangement 4500 that is configured to secure blade3100 in one or more positions relative to chassis 3010 (e.g., see FIGS.101-106). For example, the latching arrangement 4500 may secure theblade 3100 in a first extended position (see FIGS. 103-104) and in asecond extended position (see FIGS. 105-106) relative to the chassis3010. The latching arrangement 4500 includes an actuation member 4515, afirst set of releasable stops 4525, and a second set of releasable stops4535. Each of the stops 4525, 4535 is configured to move between arespective locking position and a respective releasing position.

When in the locking positions, the stops 4525, 4535 engage openings 3009(e.g., see FIG. 101) defined in the chassis 3010 to inhibit movement ofthe blade 3100 relative to the chassis 3010. When in the releasingpositions, the stops 4525, 4535 are moved out of engagement with theopenings 3009 to enable movement of the blade 3100 relative to thechassis 3010. In certain implementations, each stop 4525, 4535 isnormally biased toward a locking position relative to the chassis 3010.A user manipulates the actuation member 4515 to selectively release thestops 4525, 4535 from the respective locking positions.

In the example shown in FIG. 102, the first stops 4525 are located onfirst ends of first release arms 4520 and the second stops 4525 arelocated on first ends of second release arms 4530. In someimplementations, each of the release arms 4520, 4530 is biased towards alocking position relative to the chassis 3010. For example, each of therelease arms 4520, 4530 may be spring-biased towards the sidewalls 3011of the chassis 3010. The sidewalls 3011 inhibit the stops 4525, 4535from reaching the locking positions while the stops 4525, 4535 arespaced inwardly from the openings 3009 defined in the chassis 3010. Thechassis latching openings 3009 enable the stops 4525, 4535 to move totheir locking positions when the stop 4525, 4535 is aligned with one ofthe openings 3009.

The actuation member 4515 is configured to move relative to the blade3100 to actuate the stops 4525, 4535. The actuation member 4515 islocated at one end of an actuation arm 4510. The actuation arm 4510 alsocouples to second ends of the first and second release arms 4520, 4530.Movement of the actuation member 4515 moves the actuation arm 4510,resulting in movement of one or more of the release arms 4520, 4530,which results in movement of the respective stops 4525, 4535. In certainimplementations, the actuation member 4515 is configured to move forwardand/or rearward relative to the blade 3100 when actuated.

In some implementations, the actuation member 4515 extends forwardly ofthe blade couplers 3151, 3153 at the front of the blade 3100. Inaccordance with some aspects, the handle 3108 and the actuation member4515 are configured to be manipulated concurrently by a user using onehand. In certain implementations, the actuation member 4515 extends froma generally central portion of the front of the blade 3100. In certainimplementations, the actuation member 4515 extends over at least aportion of a blade handle 3108 that is configured to be manipulated(e.g., pulled and/or pushed) by a user. Indeed, in certainimplementations, the actuation member 4515 is configured to move alongthe handle 3108 when actuated.

In some implementations, the coupling between the release arms 4520,4530 and the actuation arm 4510 is configured to produce movement of thefirst release arms 4520 when the actuation arm 4510 is moved in a firstdirection and to produce movement of the second release arms 4530 whenthe actuation arm 4510 is moved in a second direction. In certainimplementations, the first and second directions are oppositedirections.

For example, in the implementation shown, rearward movement of theactuation member 4515 (e.g., caused by a user pushing on the actuationmember 4515 relative to the blade handle 3108) produces rearwardmovement of the actuation arm 4510 relative to the blade base 3110.Rearward movement of the actuation arm 4510 causes a retracting movementof the first release arms 4520 (as will be described in more detailherein), which moves the first stops 4525 to the respective retractedpositions. Forward movement of the actuation member 4515 (e.g., causedby a user pulling on the actuation member 4515 relative to the bladehandle 3108) produces forward movement of the actuation arm 4510relative to the blade base 3110. Forward movement of the actuation arm4510 causes a retracting movement of the second release arms 4530 (aswill be described in more detail herein), which moves the second stops4535 to releasing positions.

FIGS. 103-106 show one example blade 3100 positioned relative to anexample chassis 3010 in three positions: a closed position, a firstextended position, and a second extended position. The chassis 3010includes sidewalls 3011 and end walls 3012 that define an interior inwhich one or more blades 3100 may be installed. One or more guides 3015are positioned within the chassis 3010 to receive the blades 3100. Eachguide 3015 enables movement of one blade 3100 relative to the chassis3010. For example, each guide 3015 may enable forward and rearwardsliding movement of one blade 3100 relative to the chassis 3010.

In some implementations, the stops 4525, 4535 of a blade 3100 ride overthe guide 3015 at which the blade 3100 is received. In one exampleimplementation, the stops 4525, 4535 ride between the respective guide3015 and an adjacent guide 3015 (e.g., see FIG. 101). In certainimplementations, one or both sidewalls 3011 of the chassis 3010 define alocking opening 3009 through which one of the stops 4525, 4535 mayextend to releasably lock the blade 3100 into position relative to thechassis 3010. In the example shown, both sidewalls 3011 define anopening 3009 for each blade 3100 to be received at the chassis 3010.

In FIGS. 101 and 102, one example blade 3100 is located in the chassis3010 in the closed position. The example blade 3100 is mounted in thebottommost guide 3015 of the chassis 3010. The front couplers 3151, 3153of the blade 3100 are generally positioned at the open front of thechassis 3010. Retaining fingers 3160 extend forwardly of the frontcouplers 3151, 3153. The blade handle 3108 also extends forwardly fromthe front of the blade 3100 to enable a user to pull the blade 3100forwardly relative to the chassis 3010.

When the blade 3100 is in the closed position, the stops 4525, 4535 arepositioned inward from the locking positions. For example, the sidewalls3011 of the chassis 3010 may maintain the stops 4525, 4535 in releasingpositions. The sidewalls 3011 counteract the biasing force on therelease arms 4520, 4530 to inhibit the stops 4525, 4535 from movingcompletely to the respective locking positions. Accordingly, the firstand second stops 4525, 4535 are configured to slide against thesidewalls 3011 and over the guides 3015.

In accordance with some aspects, the blade 3100 is locked relative tothe chassis 3010 when the blade 3100 is in the closed position. In someimplementations, the blade 3100 is releasably locked relative to thechassis housing 3010. In other implementations, the blade 3100 is movedout of the closed position only when a locking force is overcome (e.g.,by a pulling force on the blade 3100). In still other implementations,the blade 3100 is not locked relative to the chassis 3010 when the blade3100 is in the closed position.

In certain implementations, one or more detents may be provided at arear of the chassis 3010 (e.g., see detents 3017 of FIG. 91). Forexample, a column of detents may be provided on (e.g., snapped intoholes defined in) at least one of the chassis side walls 3011 at therear of the chassis 3010. A notch 3105 defined in at least one of eachblade 3100 cooperates with one of the detent to inhibit movement of theblade 3100 out of the closed position until a locking force (e.g., theforce required to snap the detent out of the notch) is overcome. In oneimplementation, only one side of the blade 3100 defines a notch 3105 anddetents are provided on only one sidewall 3011 of the chassis 3010. Inother implementations, however, the detents may be provided on bothsidewalls 3011 of the chassis 3010 and the notches 3105 may be providedon both sides of the blade 3100.

In FIGS. 103 and 104, the example blade 3100 is located in the firstextended position relative to the chassis 3010. The blade base 3110 hasbeen moved (e.g., slid) forwardly along the guides 3015 from the closedposition. The front couplers 3150 of the blade 3100 are positionedforward of the open front of the chassis 3010. In some implementations,the base 3110 has been moved forwardly about one to six inches from theclosed position. In one implementation, the base 3110 has been movedforwardly about three inches. In one implementation, the base 3110 hasbeen moved forwardly about two inches. In one implementation, the base3110 has been moved forwardly about four inches.

The first stops 4525 are arranged in locking position, therebyinhibiting movement of the blade 3100 relative to the chassis 3010. Forexample, the first stops 4525 extend through the openings 3009 in thechassis sidewalls 3011 to inhibit forward or rearward movement of theblade 3100. In some implementations, the release arms 4520 bias thefirst stops 4525 through the openings 3009 when the stops 4525 arealigned with the openings 3009. In such implementations, the stops 4525automatically lock the blade 3100 into the first extended position whenthe blade 3100 reaches the first extended position. In otherimplementations, however, the stops 4525 may be configured to move tothe locking positions only when actuated by a user.

To move the blade 3100 from the first extended position (e.g., to thesecond extended position, out of the chassis, or back to the closedposition), a user manipulates the actuation member 4515 to release thefirst stops 4525. When the first stops 4525 are released, the user maypull or push the blade 3100 to a different position relative to thechassis 3010. For example, manipulating the actuation member 4515produces movement of the actuation arm 4510, which causes movement ofthe first release arms 4520, which move each of the first stops 4525 toa respective release position. In some implementations, the movement ofthe actuation arm 4510 produces movement only in the first release arms4520 and not in the second release arms 4530. In other implementations,the movement of the actuation arm 4510 also moves the second releasearms 4530.

In FIGS. 105 and 106, the example blade 3100 is located in the secondextended position relative to the chassis 3010. The blade base 3110 hasbeen moved (e.g., slid) forwardly along the guides 3015 from the firstextended position. The front couplers 3151, 3153 of the blade 3100 arepositioned farther forward of the open front of the chassis 3010 ascompared to the first extended position. A rear portion of the blade3100 is still positioned within the guides 3015 or otherwise retainedwithin the chassis 3010.

In some implementations, the base 3110 has been moved forwardly aboutone to six inches from the first extended position. In oneimplementation, the base 3110 has been moved forwardly about threeinches from the first extended position. In one implementation, the base3110 has been moved forwardly about two inches from the first extendedposition. In one implementation, the base 3110 has been moved forwardlyabout four inches from the first extended position. In someimplementations, the base 3110 has been moved forwardly about three tonine inches from the closed position. In one implementation, the base3110 has been moved forwardly about six inches from the closed position.In one implementation, the base 3110 has been moved forwardly about fiveinches from the closed position. In one implementation, the base 3110has been moved forwardly about seven inches from the closed position.

The second stops 4535 are arranged in locking positions, therebyinhibiting movement of the blade 3100 relative to the chassis 3010. Forexample, in certain implementations, the second stops 4535 extendthrough the openings 3009 in the chassis sidewalls 3011 to inhibitforward or rearward movement of the blade 3100. In some implementations,the second release arms 4530 bias the second stops 4535 through theopenings 3009 when the stops 4535 are aligned with the openings 3009. Insuch implementations, the stops 4535 automatically lock the blade 3100into the second extended position when the blade 3100 reaches the secondextended position. In other implementations, however, the second stops4535 may be configured to move to the locking position only whenactuated by a user.

To move the blade 3100 from the second extended position (e.g., out ofthe chassis or back to the closed or first extended positions), a usermanipulates the actuation member 4515 to release the second stops 4535.For example, manipulating the actuation member 4515 produces movement ofthe actuation arm 4510, which causes movement of the second release arms4530, which move each of the second stops 4535 to a respective releaseposition. In some implementations, the movement of the actuation arm4510 produces movement only in the second release arms 4530 and not inthe first release arms 4520. In other implementations, the movement ofthe actuation arm 4510 also moves the first release arms 4520.

FIGS. 107-110 show example implementations of some of the components ofthe latching system 4500. FIGS. 111-113 illustrate how these componentsare assembled on an example blade 3100. In some implementations, thecomponents of the latching arrangement 4500 are positioned over the base3110 of the blade 3100 beneath one or more of the blade components. Forexample, as shown in FIG. 100, at least a portion of the latchingarrangement 4500 may be coupled to the blade base 3110 beneath theprocessor 4140. At least a portion of the latching arrangement 4500 alsomay be coupled to the blade base 3110 beneath the circuit boardarrangement 3120. One or more cables may be routed over the latchingarrangement 4300 from the rear of the blade 3100 to be plugged into rearports of the coupler arrangement 3150 at the front of the blade 3100. Inaccordance with certain aspects, operation of the latching arrangement4500 does not interfere with the blade components.

FIG. 107 shows one example implementation of an actuation arm 4510including a first section 4511 extending from a base section 4512. Thefirst section 4511 may extend from a central portion of the base section4512. Second and third sections 4513, 4514 extend from opposite ends ofthe base section 4512. In some implementations, the second and thirdsections 4513, 4514 extend in a different direction than the firstsection 4511. In certain implementations, the second and third sections4513, 4514 extend in an opposite direction from the first section 4511.

The first section 4511 defines the actuation member 4515. For example,in some implementations, the first section 4511 may define a handle 4516or other grip portion at a distal end thereof. In one implementation,the handle 4516 is formed as a bent, rolled, or folded portion of thefirst section 4511. In other implementations, a handle 4516 may bemolded, fastened, or otherwise connected to the first section 4511. Inother implementations, the distal end of the first section 4511 may beflat.

In certain implementations, the first section 4511 also defines at leastone opening 4517 through which a fastener may extend to secure theactuation arm 4510 to the blade base 3110. As shown in FIG. 111, theblade base 3110 may define receiving members 4541 at which the fastenermay be secured. The opening 4517 is sufficiently sized and shaped toenable movement of the actuation arm 4510 relative to the fastener andreceiving member 4541. For example, the opening 4517 may define agenerally oblong shape through which the fastener may move relative tothe actuation arm 4510. In the example shown in FIG. 107, the firstsection 4511 defines two openings 4517 aligned in the direction ofmovement of the actuation arm 4510. In other implementations, greater orfewer openings 4517 may be defined in the first section 4511.

Each of the second and third sections 4513, 4514 is configured tointeract with at least one of the release arms 4520, 4530 of thelatching arrangement 4500. In some implementations, each of the secondand third sections 4513, 4514 is configured to interact with one of thefirst release arms 4520 and one of the second release arms 4530. Forexample, in certain implementations, each of the second and thirdsections 4513, 4514 defines a first opening 4518 and a second opening4519 spaced from the first opening 4518. Each of the openings 4518, 4519is configured to receive a lug or other rider of the respective releasearm 4520, 4530.

In accordance with some aspects, each of the openings 4518, 4519 of thesecond and third sections 4513, 4514 defines a camming surface. Incertain implementations, one end of each first opening 4518 defines thecamming surface and an opposite end of each second opening 4519 definesthe camming surface. In the example shown in FIG. 107, the firstopenings 4518 define camming surfaces at forward ends of the firstopenings 4518 and the second openings 4519 define camming surfaces atrearward ends of the second openings 4519. In some implementations, thecamming surfaces taper inwardly. In other implementations, the cammingsurfaces taper outwardly.

FIG. 108 shows one example implementation of a first release arm 4520including a first stop 4525 defined at one end of a body 4521. Incertain implementations, the body 4521 extends generally linearly. Inother implementations, however, the body 4521 may have any othersuitable shape (e.g., L-shaped, J-shaped, C-shaped, V-shaped, U-shaped,etc.). In the example shown, the first stop 4525 is generally cube orcuboid shaped. In other implementations, the first stop 4525 may beflat, angled, curved, or may have any other suitable shape.

The body 4521 of the first release arm 4520 is configured to interactwith the actuation arm 4510. For example, the body 4521 may define a lug4522 (FIG. 113) or other follower at a different end of the firstrelease arm 4520 from the stop 4525. In one implementation, the body4521 may define a lug 4522 at an opposite end of the first release arm4521 from the stop 4525. In certain implementations, the lug 4522extends downwardly from a section 4523 of the first release arm 4520having a reduced thickness (see FIG. 108).

Each first release arm 4520 is coupled to the blade 3100 so as to bemoveable relative to the blade base 3110. In some implementations, thefirst release arm 4520 defines at least one opening 4524 through which afastener 4543 may extend to couple the first release arm 4520 to theblade 3100. In the example shown, each fastener 4543 extends into arespective receiving structure 4542 (FIG. 111) defined on the blade base3100. In other implementations, however, the fasteners 4543 mayotherwise couple the first release arms 4520 to the blade 3100.

The opening 4524 is sufficiently sized and shaped to enable the fastener4543 to move within the opening 4524 when the first release arm 4520 ismoved relative to the blade 3100. In the example shown, each firstrelease arm 4520 defines two spaced openings 4524 within whichrespective fasteners 4543 may travel. In other implementations, eachfirst release arm 4520 may define a greater number of openings 4524.

In some implementations, each first release arm 4520 includes a spring4526 that biases the first release arm 4520 toward a locking position.In certain implementations, the springs 4526 are mounted at the openings4524 of each first release arm 4520. One end of each spring 4526 seatson a mount 4527 (FIG. 113) at one end of the opening 4524 and the otherend of each spring 4526 abuts against the fastener 4543 holding thefirst release arm 4520 to the blade 3100. The spring 4526 pushes thefirst release arm 4520 away from the fastener 4543 to move the stop 4525toward a locking position. To release the stop 4525, the first releasearm 4520 is moved counter to the bias of the spring 4526 to compress thespring 4526 toward the fastener 4543.

FIGS. 109 and 110 show example implementations of second release arms4530. The second release arm shown in FIG. 109 is flipped 180° from thesecond release arm shown in FIG. 113. Each second release arm 4530includes a second stop 4535 defined at one end of an arm body 4531. Incertain implementations, the body 4531 extends generally in an L-shape.In other implementations, however, the body 4521 may have any othersuitable shape (e.g., linear, J-shaped, C-shaped, V-shaped, U-shaped,etc.). In the example shown, the second stop 4535 is generally cube orcuboid shaped. In other implementations, the second stop 4535 may beflat, angled, curved, or may have any other suitable shape.

The body 4531 of the second release arm 4530 is configured to interactwith the actuation arm 4510. For example, the body 4531 may define a lug4532 (FIG. 113) or other follower at a different end of the secondrelease arm 4530 from the stop 4535. In one implementation, the body4531 may define a lug 4532 at an opposite end of the second release arm4531 from the stop 4535. In certain implementations, the lug 4532extends downwardly from a section 4533 of the second release arm 4530having a reduced thickness (see FIGS. 109 and 110).

Each second release arm 4530 is coupled to the blade 3100 so as to bemoveable relative to the blade base 3110. In some implementations, thesecond release arm 4530 defines at least one opening 4534 through whicha fastener 4543 may extend to couple the second release arm 4530 to theblade 3100. In the example shown, each fastener 4543 extends into arespective receiving structure 4542 (FIG. 111) defined on the blade base3100. In other implementations, however, the fasteners 4543 mayotherwise couple the second release arms 4530 to the blade 3100.

The opening 4534 is sufficiently sized and shaped to enable the fastener4543 to move within the opening 4534 when the second release arm 4530 ismoved relative to the blade 3100. In the example shown, each secondrelease arm 4530 defines two spaced openings 4534 within whichrespective fasteners 4543 may travel. In other implementations, eachsecond release arm 4530 may define a greater number of openings 4534.

In some implementations, each second release arm 4530 includes a spring4536 (FIG. 113) that biases the second release arm 4530 toward a lockingposition. In certain implementations, the springs 4536 are mounted atthe openings 4534 of each second release arm 4530. One end of eachspring 4536 seats on a mount 4537 (FIG. 113) at one end of the opening4534 and the other end of each spring 4536 abuts against the fastener4543 holding the second release arm 4530 to the blade 3100. The spring4536 pushes the second release arm 4530 away from the fastener 4543 tomove the stop 4535 toward a locking position. To release the stop 4535,the second release arm 4530 is moved counter to the bias of the spring4536 to compress the spring 4536 toward the fastener 4543.

As noted above, when a blade 3100 is located in a chassis 3010 in aclosed position, the first and second stops 4525, 4535 of the latchingarrangement 4500 are biased to abut the sidewalls 3011 of the chassis3010 (e.g., see FIGS. 101 and 102). A user moves the blade 3100 from theclosed position to a first extended position by pulling on the handle3108 of the blade 3100. The stops 4525, 4535 are maintained in theunlocked positions by the sidewalls 3011 as the blade 3100 is movedalong the guides 3015 of the chassis 3010.

When the blade 3100 reaches the first extended position, the springs4526 bias the stops 4525 of the first release arms 4520 into theopenings 3009 of the chassis 3010 (see FIGS. 103 and 104). Thespring-biased stops 4525 inhibit forward and rearward movement of theblade 3100 relative to the chassis 3010. The sidewalls 3011 of thechassis 3010 maintain the second stops 4535 in unlocked positions (seeFIGS. 103 and 104). To move the blade 3100 from the first extendedposition, a user releases (e.g., retracts) the first stops 4525 andapplies a force to (e.g., pulls or pushes on) the handle 3108 of theblade 3100.

In accordance with certain implementations, a user releases the firststops 4525 by pushing rearwardly on the actuation member 4515 relativeto the handle 3108. In certain implementations, the user pushes on theactuation member 4515 and pulls/pushes on the handle 3108 using the samehand. Indeed, in certain implementations, the user pulls/pushes on thehandle 3108 while pushing on the actuation member 4515 using the samehand.

Pushing on the actuation member 4515 moves the actuation arm 4510rearwardly relative to the blade 3100, which moves the first and secondopenings 4518, 4519 rearwardly relative to the release arms 4520, 4530.Moving the openings 4518, 4519 rearwardly causes the lug 4522 of eachfirst release arm 4520 to cam inwardly along a camming surface of therespective first opening 4518 (see FIG. 113). Camming the lugs 4522inwardly causes the first release arms 4520 to move inwardly, therebyretracting the first stops 4525 from the openings 3009 of the chassis3010. In certain implementations, the second openings 4519 of theactuation arm 4510 are sized and shaped so that the rearwardly movementof the second openings 4519 does not affect the lugs 4532 of the secondrelease arms 4530 (see FIG. 113).

When the blade 3100 reaches the second extended position, the springs4536 bias the stops 4535 of the second release arms 4530 into theopenings 3009 of the chassis 3010 (see FIGS. 105 and 106). Thespring-biased second stops 4535 inhibit forward and rearward movement ofthe blade 3100 relative to the chassis 3010 until the second stops 4535are released from the openings 3009. The first release arms 4520 arelocated outside of the chassis 3010 when the blade 3100 is in the secondextended position. Accordingly, the chassis sidewalls 3011 do notinhibit the springs 4526 of the first release arms 4520 from biasing thefirst release arms to the locking position (e.g., see FIGS. 105 and109). However, the first stops 4525 do not engage the chassis 3010 and,accordingly, do not inhibit movement of the blade 3100 relative to thechassis 3010.

To move the blade 3100 from the second extended position (e.g., out ofthe chassis or to the first extended position), a user releases (e.g.,retracts) the second stops 4535 and pulls/pushes on the handle 3108 ofthe blade 3100. In accordance with certain implementations, a userreleases the second stops 4535 by pulling on the actuation member 4515relative to the handle 4108. In certain implementations, the user pullson the actuation member 4515 and pulls on the handle 3108 using the samehand. Indeed, in certain implementations, the user pulls on the handle3108 while pulling on the actuation member 4515 using the same hand.Pulling on the actuation member 4515 moves the actuation arm 4510forwardly relative to the blade 3100, which moves the first and secondopenings 4518, 4519 forwardly relative to the release arms 4520, 4530.

Moving the actuation arm 4510 forwardly causes the lug 4532 of eachsecond release arm 4530 to cam inwardly along a camming surface of therespective second opening 4519 (see FIG. 113). Camming the lugs 4532inwardly causes the second release arms 4530 to move inwardly, therebyretracting the second stops 4535 from the openings 3009 of the chassis3010. The first openings 4518 of the actuation arm 4510 are sized andshaped so that forward movement of the first openings 4518 does notaffect the lugs 4522 of the first release arms 4520 (see FIG. 113).

FIGS. 114-117 show another example latching arrangement 4600 that isconfigured to secure a blade 3100 in one position relative to a chassis3010 (e.g., see FIGS. 114-116). For example, in one implementation, thelatching arrangement 4600 may secure the blade 3100 only in the firstextended position (see FIG. 115). In such an implementation, thelatching arrangement 4600 does not secure the blade 3100 in a closedposition or a second extended position. In another exampleimplementation, the latching arrangement 4600 may secure the blade 3100only in the second extended position (see FIG. 116). In yet anotherexample implementation, the latching arrangement 4600 may secure theblade 3100 only in the closed position (see FIG. 114).

The latching arrangement 4600 includes an actuation member 4615 and aset of releasable stops 4625. The actuation member 4615 is configured tomove relative to the blade 3100 to actuate the stops 4625. In certainimplementations, the actuation member 4615 is configured to move forwardand/or rearward relative to the blade 3100 when actuated. Movement ofthe actuation member 4615 moves an actuation arm 4610, resulting inmovement of one or more of release arms 4620, which results in movementof the respective stops 4625.

FIGS. 114-116 show one example blade 3100 positioned relative to anexample chassis 3010 in three positions: a closed position, a firstextended position, and a second extended position. As disclosed above,the chassis 3010 includes sidewalls 3011 and end walls 3012 that definean interior in which one or more blades 3100 may be installed. One ormore guides 3015 are positioned within the chassis 3010 to receive theblades 3100. In the example shown in FIG. 117, the blade 3100 is mountedin the bottommost guide 3015 of the chassis 3010. Each guide 3015enables movement of one blade 3100 relative to the chassis 3010. Forexample, each guide 3015 may enable forward and rearward slidingmovement of one blade 3100 relative to the chassis 3010. In someimplementations, the one or more stops 4625 of a blade 3100 ride overthe guide 3015 at which the blade 3100 is received. In one exampleimplementation, the stops 4625 ride between the respective guide 3015and an adjacent guide 3015.

In certain implementations, one or both sidewalls 3011 of the chassis3010 define a locking opening 3009 through which one of the stops 4625may extend to releasably lock the blade 3100 into position relative tothe chassis 3010. In the example shown, both sidewalls 3011 define anopening 3009 for each blade 3100 to be received at the chassis 3010. Incertain implementations, the openings 3009 are located at a front of thechassis sidewalls 3011. In other implementations, the openings 3009 arelocated at a central region of the chassis sidewalls 3010. In stillother implementations, the openings 3009 are located at a rear of thechassis sidewalls 3011. In still other implementations, the sidewalls3011 may define openings at front, central, and/or rear locations.

In FIG. 114, one example blade 3100 with the second latching arrangement4600 is located in the chassis 3010 in the closed position. The frontports of the coupler arrangement 3150 of the blade 3100 are generallypositioned at the open front of the chassis 3010. Retaining fingersextend forwardly of the front ports. The blade handle 3108 also extendsforwardly from the front of the blade 3100 to enable a user to pull theblade 3100 forwardly relative to the chassis 3010. The sidewalls 3011 ofthe chassis 3010 maintain the stops 4625 in releasing positions bycounteracting the biasing force on the release arms 4620. Accordingly,the stops 4625 are configured to slide against the sidewalls 3011 andover the guides 3015.

In FIG. 115, the example blade 3100 is located in the first extendedposition relative to the chassis 3010. The blade base 3110 has beenmoved (e.g., slid) forwardly along the guides 3015 from the closedposition. In some implementations, the base 3110 has been movedforwardly about one to six inches from the closed position. In oneimplementation, the base 3110 has been moved forwardly about threeinches. In one implementation, the base 3110 has been moved forwardlyabout two inches. In one implementation, the base 3110 has been movedforwardly about four inches. The stops 4625 are arranged in lockingposition, thereby inhibiting movement of the blade 3100 relative to thechassis 3010. For example, the stops 4625 extend through the openings3009 at the front of the chassis sidewalls 3011 to inhibit forward orrearward movement of the blade 3100. The front ports of the blade 3100are positioned forward of the open front of the chassis 3010.

In FIG. 116, the example blade 3100 is located in the second extendedposition relative to the chassis 3010. The blade base 3110 has beenmoved (e.g., slid) forwardly along the guides 3015 from the firstextended position. The front couplers 4150 of the blade 3100 arepositioned farther forward of the open front of the chassis 3010 ascompared to the first extended position. A rear portion of the blade3100 is still positioned within the guides 3015 or otherwise retainedwithin the chassis 3010.

In some implementations, the blade 3100 has been moved forwardly aboutone to six inches from the first extended position. In oneimplementation, the blade 3100 has been moved forwardly about threeinches from the first extended position. In one implementation, theblade 3100 has been moved forwardly about two inches from the firstextended position. In one implementation, the blade 3100 has been movedforwardly about four inches from the first extended position. In someimplementations, the blade 3100 has been moved forwardly about three tonine inches from the closed position. In one implementation, the blade3100 has been moved forwardly about six inches from the closed position.In one implementation, the blade 3100 has been moved forwardly aboutfive inches from the closed position. In one implementation, the base3110 has been moved forwardly about seven inches from the closedposition.

A user moves the blade 3100 between the positions using a blade handle3108. For example, a user may push or pull on a forwardly extendingblade handle 3108. In some implementations, the blade handle 3108extends forwardly of the blade 3100 from a central portion at the frontof the blade 3100. In other implementations, the blade handle 3108 mayextend forwardly of the blade 3100 from a side portion at the front ofthe blade 3100. In other implementations, the blade handle 3108 mayextend from a side or rear of the blade 3100. In still otherimplementations, the two or more blade handles 4108 may extend from theblade 3100.

To move the blade 3100 from a latched position (e.g., from the firstextended position shown in FIG. 115), a user manipulates the actuationmember 4615 of the latching arrangement 4600 to release the stops 4625.When the stops 4625 are released, the user may pull or push the bladehandle 3108 to move the blade 3100 to a different position relative tothe chassis 3010. In some implementations, the actuation member 4615defines a handle or other grip portion for the user. In certainimplementations, the handle is formed as a bent, rolled, or foldedportion of the actuation member 4615. In other implementations, a handlemay be molded, fastened, or otherwise connected to the actuation member4615. In still other implementations, the distal end of the actuationmember 4615 may be flat.

In accordance with other aspects, the handle 3108 and actuation member4615 are configured to be manipulated using one hand. In accordance withsome aspects, the handle 3108 and the actuation member 4615 areconfigured to be manipulated concurrently by a user. For example, insome implementations, the actuation member 4615 extends forwardly of theblade 3100. In certain implementations, the actuation member 4615extends over at least a portion of a blade handle 3108. Indeed, incertain implementations, the actuation member 4615 is configured to movealong the handle 3108 when actuated.

In some implementations, a user releases the stops 4625 by pushingrearwardly on the actuation member 4615 relative to the handle 3108. Inother implementations, a user releases the stops 4625 by pushingforwardly on the actuation member 4615 relative to the handle 3108. Forexample, in certain implementations, the user pulls/pushes on the handle3108 while pushing/pulling on the actuation member 4615 using the samehand. In still other implementations, the user releases the stops 4625by otherwise manipulating the actuation member 4615.

As noted above, moving the actuation member 4615 produces movement ofthe actuation arm 4610. Each release arm 4620 is operably coupled to theactuation arm 4610. Each of the release arms 4620 is configured to movethe respective stop 4625 between a respective locking position and arespective releasing position when operated by the actuation arm 4610.When in the locking positions, each stop 4625 engages an opening 3009defined in the chassis 3010 to inhibit movement of the blade 3100relative to the chassis 3010. When in the releasing position, the stop4625 is moved out of engagement with the openings 3009 to allow movementof the blade 3100 relative to the chassis 3010.

Each release arm 4620 is coupled to the blade 3100 so as to be moveablerelative to the blade base 3110. In some implementations, each releasearm 4620 defines at least one opening 4624 through which a fastener 4643(FIG. 115) may extend to couple the release arm 4620 to the blade 3100.In the example shown, each fastener 4643 extends into a respectivereceiving structure defined on the blade base 3100. In otherimplementations, however, the fasteners 4643 may otherwise couple therelease arms 4620 to the blade 3100. Each opening 4624 is sufficientlysized and shaped to enable the fastener 4643 to move within the opening4624 when the release arm 4620 is moved relative to the blade 3100.

In certain implementations, each stop 4625 of the latching arrangement4600 is normally biased toward a locking position relative to thechassis 3010. In such implementations, the stops 4625 automaticallylatch the blade 3100 into position when the blade 3100 is locatedrelative to the chassis 3010 to align the stops 4625 and the chassisopenings 3009. In some implementations, each release arm 4620 includes aspring 4626 that biases the stop 4625 toward a locking position. Incertain implementations, the springs 4626 are mounted at the openings4624 of each release arm 4620. One end of each spring 4626 seats on amount 4627 (FIG. 114) at one end of the opening 4624 and the other endof each spring 4626 abuts against the fastener 4643 holding the releasearm 4620 to the blade 3100. The spring 4626 pushes the release arm 4620away from the fastener 4643 to move the stop 4625 toward a lockingposition. In other implementations, however, the stops 4625 may beconfigured to move to the locking positions only when actuated by auser.

In some implementations, one or more release arms 4620 and stops 4625are substantially the same as the first release arms 4520 and firststops 4525 disclosed herein. In other implementations, one or morerelease arms 4620 and stops 4625 are substantially the same as thesecond release arms 4530 and second stops 4535 disclosed herein. Instill other implementations, the arms 4620 and stops 4625 have adifferent configuration from the release arms 4520, 4530 and stops 4625,4635 disclosed herein.

In some implementations, the stops 4625 are located at a generallycentral region of the blade base 3110 between the front and rear of theblade 3100 (see FIG. 114). In other implementations, the stops 4625 maybe located at the rear of the blade base 3110 (e.g., see the secondstops 4535 of FIG. 99), at the front of the blade base 3110, or at anyother suitable location on the blade 3100.

In the example shown, the latching arrangement 4600 includes two releasearms 4620. In other implementations, the latching arrangement 4600 maydefine greater or fewer release arms 4620. Each release arm 4620 definestwo spaced openings 4624 within which respective fasteners 4643 maytravel. In other implementations, each release arm 4620 may define agreater number of openings 4624.

To release the stop 4625, the release arm 4620 is moved counter to thebias of the release arms 4620. The release arm 4620 is configured toengage and be operated by the actuation arm 4610. For example, therelease arm 4620 may define a lug or other follower at a different endof the release arm 4620 from the stop 4625. In one implementation, therelease arm 4620 may define a lug at an opposite end of the release arm4620 from the stop 4625. In certain implementations, the lug extendsdownwardly from a section of the release arm 4620 having a reducedthickness (see FIG. 117). The lug extends through an opening defined inthe actuation arm 4610.

For example, the actuation arm 4610 may include one or more sectionsthat are each configured to interact with the lug of a release arm 4620.In certain implementations, each of the actuation arm sections definesat least one opening configured to receive a lug or other follower ofthe respective release arm 4620. In accordance with some aspects, eachof the openings defines a camming surface. In the example shown in FIGS.114-116, the actuation arm sections define camming surfaces at forwardends of the openings. In other implementations, however, the actuationarm sections define camming surfaces at rearward ends of the secondopenings. In some implementations, the camming surfaces taper inwardly.In other implementations, the camming surfaces taper outwardly.

In certain implementations, the actuation arm 4610 also is movablyfastened to the blade 3100. For example, one or more fastener may extendthrough one or more openings defined in the actuation arm 4610 to securethe actuation arm 4610 to the blade base 3110. For example, the bladebase 3110 may define receiving members at which the fastener 4643 may besecured. The opening is sufficiently sized and shaped to enable movementof the actuation arm 4610 relative to the fastener and receiving member.For example, the opening may define a generally oblong shape throughwhich the fastener 4643 may move relative to the actuation arm 4610.

A user moves the actuation arms 4620 to selectively release the stops4625 from the respective locking positions. In the example shown inFIGS. 114-117, pushing on the actuation member 4615 moves the actuationarm 4610 rearwardly relative to the blade 3100, which moves openingsdefined in the actuation arm 4610 rearwardly relative to the releasearms 4620. Moving the openings rearwardly causes the lug of each releasearm 4620 to cam inwardly along a camming surface of the respectiveopening. Camming the lugs inwardly causes the release arms 4620 to moveaway from the respective sidewall 3011, thereby retracting the stops4625 from the openings 3009 of the chassis 3010.

In accordance with some aspects, the blade 3100 may be locked relativeto the chassis 3010 when the blade 3100 is in the closed positionwithout using the latching arrangement 4600. In some implementations,the blade 3100 is moved out of the closed position only when a lockingforce is overcome. For example, in certain implementations, one or moredetents may be provided at a rear of the chassis 3010. A notch 3105defined in at least one of each blade 3100 cooperates with one of thedetent to inhibit movement of the blade 3100 out of the closed positionuntil a locking force (e.g., the force required to snap the detent outof the notch) is overcome.

FIGS. 118-127 show another example bladed chassis system 5000 includingan example chassis 5010 that is configured to receive one or more blades3100. The chassis 5010 includes sidewalls 5011 and end walls 5012 thatdefine an interior in which one or more blades 3100 may be installed.One or more guides 5015 are positioned within the chassis 5010 toreceive the blades 3100. Each guide 5015 enables movement of one blade3100 relative to the chassis 5010. For example, each guide 5015 mayenable forward and rearward sliding movement of one blade 3100 relativeto the chassis 5010.

In certain implementations, one or both sidewalls 5011 of the chassis5010 each define at least one locking opening 5009. In the exampleshown, each sidewall 5011 defines a front opening 5009A, an intermediateopening 5009B, and a rear opening 5009C for each blade 3100 to bereceived at the chassis 5010. The front openings 5009A are located atthe front of the chassis sidewalls 5011, the intermediate openings 5009Bare located at middle portions of the chassis sidewalls 5011, and therear openings 5009C are located at the rear of the chassis sidewalls5011. In other implementations, each sidewall 5011 may define greater orfewer openings 5009.

In accordance with some aspects, each blade 3100 includes an examplelatching arrangement 5500 configured to secure the blade 3100 in one ormore positions relative to a chassis 5010. For example, the examplelatching arrangement 5500 may secure the blade in a closed position, afirst extended position, and/or a second extended position relative tothe chassis 5010 (e.g., see FIGS. 120-122). The latching arrangement5500 includes an actuation member 5515 and a set of releasable stops5525 that selectively extend through the openings 5009 of the chassis5010 to releasably lock the blade 3100 into position relative to thechassis 5010.

Each of the stops 5525 is configured to move between a respectivelocking position and a respective releasing position. When in thelocking positions, each stop 5525 engages one of the openings 5009defined in the chassis 5010 to inhibit movement of the blade 3100relative to the chassis 5010. When in the releasing positions, the stops5525 are moved out of engagement with the openings 5009 to enablemovement of the blade 3100 relative to the chassis 5010. When the blade3100 moves relative to the chassis 5010, the stops 5525 of a blade 3100ride over the guide 5015 at which the blade 3100 is received. In oneexample implementation, the stops 5525 ride between the respective guide5015 and an adjacent guide 5015 (e.g., see FIG. 120).

In certain implementations, each stop 5525 is normally biased toward alocking position relative to the chassis 5010. A user manipulates theactuation member 5515 to selectively release the stops 5525 from therespective locking positions. In the example shown in FIG. 118, movingthe actuation member 5515 rearwardly relative to the blade 3100 retractsthe stops 5525 inwardly relative to the blade 3100. In otherimplementations, however, the latching arrangement 5500 is configured sothat forward movement of the actuation member 5515 retracts the stops5525. In still other implementations, the latching arrangement 5500 isconfigured so that another type of movement (e.g., vertical, sideways,diagonal, rotational, etc.) of the actuation member 5515 retracts thestops 5525.

FIGS. 120-122 show one example blade 3100 positioned relative to anexample chassis 5010 in three positions: a closed position, a firstextended position, and a second extended position. A user moves theblade 3100 between the positions using a blade handle 3108. For example,a user may push or pull on a forwardly extending blade handle 3108. Insome implementations, the blade handle 3108 extends forwardly of theblade 3100 from a central portion at the front of the blade 3100. Inother implementations, the blade handle 3108 may extend forwardly of theblade 3100 from a side portion at the front of the blade 3100. In otherimplementations, the blade handle 3108 may extend from a side or rear ofthe blade 3100. In still other implementations, the two or more bladehandles 3108 may extend from the blade 3100.

In FIG. 120, one example blade 3100 with the second latching arrangement5500 is located in the chassis 5010 in the closed position. In theexample shown, the blade 3100 is mounted in the bottommost guide 5015 ofthe chassis 5010. The front ports of the coupler arrangement 3150 of theblade 3100 are generally positioned at the open front of the chassis5010. Retaining fingers 3160 extend forwardly of the front ports. Theblade handle 3108 also extends forwardly from the front of the blade3100 to enable a user to pull the blade 3100 forwardly relative to thechassis 5010. The stops 5525 extend through the rear openings 5009C inthe chassis sidewalls 5011, thereby inhibiting movement of the blade3100 relative to the chassis 5010.

In FIG. 121, the example blade 3100 is located in the first extendedposition relative to the chassis 5010. The blade base 3110 has beenmoved (e.g., slid) forwardly along the guides 5015 from the closedposition. The front ports of the blade 3100 are positioned forward ofthe open front of the chassis 5010. The stops 5525 extend through theintermediate openings 5009B in the chassis sidewalls 5011, therebyinhibiting movement of the blade 3100 relative to the chassis 5010. Insome implementations, the base 3110 has been moved forwardly about oneto six inches from the closed position. In one implementation, the base3110 has been moved forwardly about three inches. In one implementation,the base 3110 has been moved forwardly about two inches. In oneimplementation, the base 3110 has been moved forwardly about fourinches.

In FIG. 122, the example blade 3100 is located in the second extendedposition relative to the chassis 5010. The blade base 3110 has beenmoved (e.g., slid) forwardly along the guides 5015 from the firstextended position. The front ports of the blade 3100 are positionedfarther forward of the open front of the chassis 5010 as compared to thefirst extended position. A rear portion of the blade 3100 is stillpositioned within the guides 5015 or otherwise retained within thechassis 5010. The stops 5525 extend through the front openings 5009A inthe chassis sidewalls 5011, thereby inhibiting movement of the blade3100 relative to the chassis 5010.

In some implementations, the blade 3100 has been moved forwardly aboutone to six inches from the first extended position. In oneimplementation, the blade 3100 has been moved forwardly about threeinches from the first extended position. In one implementation, theblade 3100 has been moved forwardly about two inches from the firstextended position. In one implementation, the blade 3100 has been movedforwardly about four inches from the first extended position. In someimplementations, the blade 3100 has been moved forwardly about three tonine inches from the closed position. In one implementation, the blade3100 has been moved forwardly about six inches from the closed position.In one implementation, the blade 3100 has been moved forwardly aboutfive inches from the closed position. In one implementation, the blade3100 has been moved forwardly about seven inches from the closedposition.

To move the blade 3100 from a latched position (e.g., from the firstextended position shown in FIG. 121 or from the second extended positionshown in FIG. 122), a user manipulates the actuation member 5515 of thelatching arrangement 5500 to release the stops 5525. When the stops 5525are released, the user may pull or push the blade handle 3108 to movethe blade 3100 to a different position relative to the chassis 5010. Insome implementations, the actuation member 5515 defines a handle orother grip portion for the user. In certain implementations, the handleis formed as a bent, rolled, or folded portion of the actuation member5515. In other implementations, a handle may be molded, fastened, orotherwise connected to the actuation member 5515. In still otherimplementations, the distal end of the actuation member 5515 may beflat.

In accordance with other aspects, the handle 5508 and actuation member5515 are configured to be manipulated using one hand. In accordance withsome aspects, the handle 3108 and the actuation member 5515 areconfigured to be manipulated concurrently by a user. For example, insome implementations, the actuation member 5515 extends forwardly of theblade 3100. In certain implementations, the actuation member 5515extends over at least a portion of a blade handle 3108. Indeed, incertain implementations, the actuation member 5515 is configured to movealong the handle 3108 when actuated.

FIGS. 123-125 show example implementations of some of the components ofthe latching system 5500. The latching system 5500 includes an actuationarm 5510, at least one release arm 5520, and at least one swing arm 5570operably connecting the actuation arm 5510 to the release arm 5520. Theswing arm 5570 operates so that forward and/or rearward movement of theactuation arm 5510 results in a retracting motion of the release arms5520. In the example shown, the latching system 5500 includes tworelease arms 5520 and two swing arms 5570. In other implementations,however, the latching system 5500 may include a greater or fewer numberof release arms 5520 and swing arms 5570.

The actuation arm 5510 is configured to move forwardly and/or rearwardlyrelative to the blade 3100. The release arms 5520 are configured to moverelative to the blade 3100 to extend and retract the stops 5525. Theswing arms 5570 are configured to rotate at least partially relative tothe blade 3100. In accordance with some aspects, forward and/or rearwardmovement of the actuation arm 5510 causes the swing arms 5570 to rotate,which causes the extension and retraction of the stops 5525 (see FIG.118). In certain implementations, the actuation arm 5510 and the releasearms 5520 slidably move along the base 3110 of the blade 3100.

FIGS. 126-127 illustrate how these components are assembled on anexample blade 3100. In some implementations, the components of thelatching arrangement 5500 are positioned over the base 3110 of the blade3100 beneath one or more of the blade components. For example, as shownin FIG. 118, at least a portion of the latching arrangement 5500 may becoupled to the blade base 3110 beneath the processor 3140. At least aportion of the latching arrangement 5500 also may be coupled to theblade base 3110 beneath the circuit board arrangement 3120. One or morecables may be routed over the latching arrangement 5500 from the rear ofthe blade 3100 to be plugged into rear ports of the coupler arrangement3150 at the front of the blade 3100. In accordance with certain aspects,operation of the latching arrangement 5500 does not interfere with theblade components.

FIG. 123 shows one example implementation of an actuation arm 5510including a body 5511 defining the actuation member 5515 extending in afirst direction and at least one prong 5513 extending in a seconddirection. In some implementations, the body 5511 of the actuation arm5510 also includes a second prong 5514. In certain implementations, thesecond prong 5514 extends in a different direction from the first prong5513. In certain implementations, each prong 5513, 5514 extends in adifferent direction from the actuation member 5515. For example, in oneimplementation, the body 5511 defines a Y-shape.

In some implementations, the actuation member 5515 defines a handle 5516or other grip portion at a distal end thereof. In one implementation,the handle 5516 is formed as a bent, rolled, or folded portion at thedistal end of the actuation member 5515. In other implementations, ahandle 5516 may be molded, fastened, or otherwise connected to thedistal end of the actuation member 5515. In other implementations, thedistal end of the actuation member may be flat.

In certain implementations, the body 5511 of the actuation arm 5510 alsodefines at least one opening 5512 through which a fastener may extend tosecure the actuation arm 5510 to the blade base 3110. As shown in FIG.126, the blade base 3110 may define one or more receiving members 5541at which the fastener may be secured. The opening 5512 is sufficientlysized and shaped to enable movement of the actuation arm 5510 relativeto the fastener and receiving member 5541. For example, the opening 5512may define a generally oblong shape through which the fastener may moverelative to the actuation arm 5510. In the example shown in FIG. 123,the body 5511 defines two openings 5512 aligned in the direction ofmovement of the actuation arm 5510. In other implementations, greater orfewer openings 5512 may be defined in the body 5511.

Each of the prongs 5513, 5514 is configured to operably connect to atleast one of the release arms 5520 of the latching arrangement 5500. Forexample, in certain implementations, each of the prongs 5513, 5514includes a lug 5516 or other guide member extending upwardly from thebody 5511. The lugs 5516 are configured to interact with the swing arms5570, which are configured to interact with the release arms 5520 aswill be described in more detail herein. In certain implementations,each prong 5513, 5514 includes one lug 5516 located ata distal end ofthe prong 5513, 5514. In one implementation, the lug 5516 includes ahollow cylinder. In other implementations, the lug 5516 may include asolid bump or other protrusion.

FIG. 124 shows one example implementation of a release arm 5520including a stop 5525 defined at one end of a body 5521. In certainimplementations, the body 5521 extends generally linearly. In otherimplementations, however, the body 5521 may have any other suitableshape (e.g., L-shaped, J-shaped, C-shaped, V-shaped, U-shaped, etc.). Inthe example shown, the release arm body 5521 includes a generally linearextension section 5527, a raised section 5523 at one end of theextension section 5527, and an angled section 5526 at another end of theextension section 5527.

Each release arm 5520 is coupled to the blade 3100 so as to be moveablerelative to the blade base 3110. In some implementations, the extensionsection 5527 of the release arm 5520 defines at least one opening 5524through which a fastener 5543 (FIG. 126) may extend to couple therelease arm 5520 to the blade 3100. In the example shown, each fastener5543 extends into a respective receiving structure 5542 (FIG. 126)defined on the blade base 3110. In other implementations, however, thefasteners 5543 may otherwise couple the release arms 5520 to the blade3100. The opening 5524 is sufficiently sized and shaped to enable thefastener 5543 to move within the opening 5524 when the release arm 5520is moved relative to the blade 3100. In the example shown, each firstrelease arm 5520 defines one opening 5524 within which a fastener 5543may travel. In other implementations, each release arm 5520 may definetwo or more openings 5524.

Each stop 5525 is located at the angled section 5526 of one of therelease arms 5520. In some implementations, the stop 5525 is integralwith the angled section 5526. In other implementations, the stop 5525 isfastened to the angled section 5526. In one implementation, the firststop 5525 is generally cube or cuboid shaped. In the example shown, thecuboid stop 5525 is oriented so that two surfaces of the stop 5525aligned with the chassis openings 5009 and two surfaces aligned with thefront and rear of the chassis 5010. In other implementations, the stops5525 may be flat, angled, curved, or may have any other suitable shape.

The raised section 5523 of the release arm 5520 is configured torotatably connect to a respective one of the swing arms 5570. Forexample, in certain implementations, the raised section 5523 defines anopening 5522 at which the release arm 5520 connects to the swing arm5570. In some implementations, the raised section 5523 has the samethickness as the extension section 5527. In other implementations, theraised section 5523 has a reduced thickness as compared to the extensionsection 5527.

FIG. 125 shows one example implementation of a swing arm 5570 that isconfigured to operably couple together a release arm 5520 to theactuation arm 5510. In accordance with some aspects, the swing arms 5570translate movement of the actuation member 5515 in one direction intomovement of the stops 5525 in a different direction. For example, theswing arms 5570 may translate rearward motion of the actuation member5515 relative to the blade 3100 into a retracting motion of the stops5525 relative to the chassis sidewalls 5011. The swing arm 5570 includesa mounting section 5571 by which the swing arm 5570 may be rotatablyconnected to the blade 3100. For example, the mounting section 5571 maydefine a mounting opening 5572 through which a fastener may extend toconnect the swing arm 5570 to the blade 3100. The swing arm 5570 isconfigured to be selectively rotated at least partially relative to theblade 3100.

One end of the swing arm 5570 includes a first connection section 5573at which the swing arm 5570 may be coupled to the actuation arm 5510.For example, in certain implementations, the first connection section5573 defines an opening 5574 through which the lug 5516 of the actuationarm 5510 may extend to rotatably couple the swing arm 5570 to theactuation arm 5510. Another end of the swing arm 5570 includes a secondconnection section 5575 at which the swing arm 5570 may be coupled tothe release arm 5520. For example, in certain implementations, thesecond connection section 5575 includes one or more lugs 5576 that areconfigured to extend through the opening 5522 defined in the release arm5520.

In some implementations, each swing arm 5570 is biased towards aninitial position. For example, in certain implementations, each swingarm 5570 is biased towards a position at which the lugs 5576 push theraised section 5523 of the release bar 5520 to bias the stops 5525 intothe locking position. In some such implementations, each of the stops5525 is biased through one of the openings 5009 when the stop 5525 isaligned with the openings 5009. In such implementations, the stops 5525automatically lock the blade 3100 into a predetermined position when theblade 3100 reaches the predetermined position. In other implementations,however, the stops 5525 may be configured to move to the lockingpositions only when actuated by a user.

In certain implementations, each swing arm 5570 includes a spring 5578(FIG. 126) that biases the swing arm 5570 towards the initial position.In certain implementations, the springs 5528 are mounted beneath themounting sections 5571 of the swing arms 5570. In some implementations,the swing arms 5570 have a planar configuration. In otherimplementations, the mounting section 5571 of the swing arm 5570 israised (e.g., stepped) above the first and second connection sections todefine a space at which the spring 5578 may be mounted. In the exampleshown, the spring 5578 is a torsion spring. In other implementations,however, the spring 5578 may be any type of spring that will apply arotational or pivotal load to the swing arm 5570. In still otherimplementations, springs may be mounted directly to the release arms5520 to bias the stops 5525 to the locking positions, with or withoutthe swing arm springs 5578.

A user releases the stops 5525 from the chassis openings 5009 by movingthe actuation arm 5510, to rotate the swing arms 5570, to retract therelease arms 5520. The user applies sufficient force to the actuationarm 5510 to overcome the biasing force applied to the swing arms 5570.In certain implementations, the actuation member 4515 is configured tomove forward and/or rearward relative to the blade 3100 when actuated.

For example, in the implementation shown, rearward movement of theactuation member 5515 with sufficient force to overcome the bias of thesprings 5578 produces rearward movement of the actuation arm 5510relative to the blade base 3110. In certain implementations, therearward movement is caused by a user pushing on the actuation member5515 relative to the blade handle 3108. Rearward movement of theactuation arm 5510 applies a rotational force to the swing arms 5570. Inthe example shown, the rearward movement of the actuation arm 5510applies a clockwise rotational force to the right-most release arm 5520and a counter-clockwise rotational force to the left-most release arm5520.

The rotational movement of the swing arms 5570 produces a slidingmovement of each release arm 5520. In the example shown, the rotationalmovements of the swing arms 5570 produce forward and inward movements ofthe release member 5520. In certain implementations, the release arms5520 slide diagonally across the blade base 3110. The inward motion ofthe release arms 5520 retracts the stops 5525 from the chassis sidewalls5011. In some implementations, the inward motion of the release arms5520 pulls the stops 5525 substantially sideways relative to the chassis5010. In one implementation, the release arms 5520 are configured topull the stops 5525 sideways only. In other implementations, the inwardmotion of the release arms 5520 pulls the stops 5525 partially forwardand partially sideways.

Releasing the actuation member 5515 enables the springs 5578 to bias theswing arms 5570 back to the initial positions. The return movement ofthe swing arms 5570 pushes the actuation arm 5510 forward. The returnmovement of the swing arms 5570 also pushes the release arms 5520outwardly, thereby biasing the stops 5525 back towards the lockingpositions. In certain implementations, the return movement of the swingarms 5570 pushes the release arms 5520 rearwardly and outwardly.

To move the blade 3100 from the closed position (FIG. 120) to the firstextended position, a user grasps the handle 3108 and pushes rearwardlyon the actuation member 5515. When the stops 5525 retract from the rearopenings 5009C, the user pulls on the handle 3108 to move the blade 3100forward relative to the chassis 5010. In some implementations, the userreleases the actuation member 5515 when the blade 3100 is movedsufficiently forward so that the stops 5525 clear the rear openings5009C. In such implementations, the stops 5525 are biased towards thechassis walls 5011 as the blade 3100 slides within the chassis 5010.When the user has moved the blade 3100 to the first extended position,the stops 5525 snap into the intermediate openings 5009B defined in thechassis 5010.

In other implementations, the user retains the actuation member 5515 inthe rearward position. In such implementations, the stops 5525 remain inthe releasing positions as the blade 3100 moves relative to the chassis5010. When the user pulls the blade 3100 to the desired position (e.g.,the first extended position), the user releases the actuation member5515 to enable the stops 5525 to extend into the appropriate openings(e.g., the intermediate openings 5009B) defined in the chassis 5010. Ofcourse, the user also may pull the blade 3100 to the second extendedposition before releasing the actuation member 5515. In suchimplementations, the stops 5525 will extend into the front openings5009A when released. In still other implementations, the user may pullthe blade 3100 out of the chassis 5010.

In accordance with some aspects, one or more blades positioned in thechassis 3010 may be “smart” blades. As the term is used herein, a“smart” blade is a blade having PLI functionality. Smart blades mayinclude a circuit board arrangement, a blade processor, and one or more“smart” couplers. The smart couplers include one or more media readinginterfaces configured to read physical layer information stored on or inphysical media segments. The blade processor may manage the mediareading interfaces via the circuit board arrangement.

A smart blade may be installed at a “smart” chassis, which includes abackplane (e.g., chassis backplane 3040 of FIG. 91). The circuit boardarrangement of each smart blade connects the blade processors to thebackplane. A chassis processor (e.g., chassis processor 3060 of FIG. 48)connects to the blade processors via the backplane. The chassisprocessor may be connected to a data network. For example, FIG. 91illustrates one example smart chassis 3010 having a backplane 3040including multiple blade ports 3042. Each blade port 3042 is configuredto connect to the circuit board arrangement of any smart bladepositioned in the chassis 3010.

In accordance with other aspects, one or more of the blades may be“passive” blades. As the term is used herein, a “passive” blade is ablade that does not have PLI functionality. For example, in someimplementations, a passive blade may have one or more “passive” couplersthat do not include media reading interfaces as will be described inmore detail herein. In certain implementations, the passive blade doesnot have a circuit board arrangement or a blade processor.

In accordance with some aspects, a passive blade may be installed at asmart chassis. For example, the passive blade may have the same orsimilar dimensions of the smart blade to enable the passive blade to fitwithin the smart chassis. In other implementations, the passive blademay be installed at a “passive” chassis. As the term is used herein, a“passive” chassis is a chassis that does not include a backplane or achassis processor. In certain implementations, a smart blade may beinstalled at the passive chassis.

FIGS. 128-142 illustrate various example implementations of smart blades6100. In general, the smart blade 6100 includes a base 6110 that is thesame as the base 3110 of blade 3100 of FIGS. 54-127. The smart blade6100 also includes a circuit board arrangement 6120, a blade processor6140, retention fingers 6160, and latching tabs 6170 that aresubstantially the same as the circuit board arrangement 3120, bladeprocessor 3140, retention fingers 3160, and latching tabs 3170 of blade3100. The blade processor 6140 connects to the chassis backplane (e.g.,chassis backplane 3040 of FIG. 91) via the circuit board arrangement6120 as will be described in more detail herein.

In the example shown, the example blade 6100 includes a plurality ofsmart couplers 6151 at the front of the blade 6100. Each smart coupler6151 includes one or more media reading interfaces 6158. The mediareading interfaces of the smart couplers 6151 are coupled to the circuitboard arrangement 6120 of the blade 6100. The blade processor 6140 alsois coupled to the circuit board arrangement 6120 (see FIG. 128). Aconnection end 6125 (FIG. 131) of the circuit board arrangement 6120 isplugged into one of the blade ports 3042 of the backplane 3040 (e.g.,see connection end 3125 of blade 3100 plugged into port 3042 in FIG.91). In various implementations, the connection end 6125 of the circuitboard 6120 and the backplane 3040 forms a card edge connection, aplug/socket connection, a cable connection, a wireless connection, oranother type of connection.

In some implementations, the media reading interface determines that amedia segment 6250 has been received at a port of the smart coupler6151. For example, a media reading interface at a front port of theblade 6100 may determine when an outgoing media segment 3220 has beenreceived at the front port. In other implementations, each media readinginterface of a smart coupler 6151 forms an electrical connection betweena storage device 6254 of a media segment 6250 and the circuit boardarrangement 6120 of the blade 6100 (see FIG. 129). For example, thestorage device 6254 may store physical layer information about the mediasegment 6250.

The media reading interfaces are electrically connected (or otherwisecommunicatively coupled) to the blade processor 6140. The bladeprocessors 6140 connect to the data network via the chassis backplane3040 and the chassis processor 3060. In some implementations, each bladeprocessor 6140 operates the media reading interfaces of each blade 6100.In some such implementations, the chassis processor 3060 is a masterprocessor that connects to and manages the blade processors 6140 of theblades 6100 in the chassis 3010. For example, the chassis processor 3060can instruct each of the blade processors 6140 to determine whichcommunications couplers 6150 have media segments 3200 inserted therein,to obtain physical layer information from the media segments 3200, or toforward the physical layer information to the chassis processor 3060 forstorage and/or transmission to the data network.

FIGS. 129A and 129B show example implementations of smart couplers 6151including example media reading interfaces 6158. The smart coupler 6151of FIG. 129A is configured to receive two or more LC-type opticalconnectors and the smart coupler 6151 of FIG. 129B is configured toreceive two MPO-type optical connectors. In general, each media readinginterface 6158 is formed from one or more contact members 6159. As shownin FIG. 129B, some types of coupler bodies 6151 defines slots 6154configured to receive the one or more contact members 6159. As shown inFIG. 129A, portions of the contact members 6159 extend into thethrough-passages of the couplers 6151 to engage the electrical contactsof the storage devices 6254 of the fiber optic connector 6250. Otherportions of the contact members are configured to engage contacts on aprinted circuit board 6120 (FIG. 129A) associated with (e.g., positionedon top of) the coupler 6151. As discussed above, the blade processor6140 also can be electrically coupled to the printed circuit board 6120for locally managing the media reading interfaces 6158. Such a processor6140 can communicate with the memory circuitry on the connector storagedevices 6254 via the contact members and the printed circuit boardarrangement 6120.

FIGS. 130A and 130B show example implementations of physical mediasegments 6250 configured to terminate at least one optical fiber. FIG.130A shows a physical media segment 6250 implemented as an LC-type fiberoptic connector and FIG. 130B shows a physical media segment 6250implemented as an MPO-type fiber optic connector. Each fiber opticconnector 6250 includes a body 6251 enclosing an optical ferrule 6252through which at least one optical fiber extends. The body 6251 alsoincludes a key area 6253 at which the storage device 6254 may bepositioned. For example, the key area 6253 may define a depression orcavity in which a storage device 6254 can be positioned. In accordancewith some implementations, the storage device 6254 includes memorycircuitry (e.g., an EEPROM chip) arranged on a printed circuit board.Electrical contacts also are arranged on the printed circuit board forinteraction with the media reading interface 6158 of the smart coupler6151.

Additional information pertaining to some example fiber optic connectors6250, storage devices 6254, fiber optic adapters 6151, and contactmembers can be found in copending U.S. provisional Application Nos.61/303,961; 61/413,828; 61/437,504; and U.S. Pat. No. 8,690,593incorporated by reference above.

FIGS. 131-142 illustrate various example bladed panel systems in whichthe smart couplers 6151 of the blades 6100 remain electrically connectedto a chassis backplane 3040 while the blades 6100 move relative to thechassis 3010 between at least two positions. For example, the couplers6151 may remain electrically connected to the backplane 3040 as theblade 6100 moves between the closed and first extended positions. Insome implementations, the example blade 6100 includes a circuit boardarrangement 6120 having at least a first board 6122 and a second board6124. The smart couplers 6151 defining the front ports of the blade 6100connect to the first board 6122. The connection end 6125 of the circuitboard arrangement 6125 is defined by the second board 6124.

The blade 6100 also includes a first connection system 6130 thatelectrically connects the first board 6122 and the second board 6124.The first connection system 6130 also enables movement between the firstboard 6122 and the second board 6124 without disrupting the electricalconnection between the two boards 6122, 6124. The first connectionsystem 6130 enables the circuit board arrangement 6120 to remainconnected to the backplane 3040 of the chassis 3010 during movement ofthe blade 6100. Accordingly, the chassis processor 3060 may manage themedia reading interfaces 6158 of the smart couplers 6151 when the blade6100 has been moved to the first extended position (e.g., to facilitateinsertion and/or removal of media segments at the front ports.

In general, each connection assembly 6130 includes a first portionsecured to the first circuit board 6122 and a second portion secured tothe second circuit board 6124. The first portion of the connectionassembly 6130 is moveably secured to the second portion. For example,the first portion of certain types of connection assemblies 6130 isslideably secured to the second portion. Certain types of connectionassemblies 6130 also include a flexible electrical connector thatmaintains an electrical connection between the first board 6122 and thesecond board 6124.

FIGS. 131-135 illustrate one example connection assembly 6130 suitablefor use with a blade 6100. The connection assembly 6130 includes atleast a first mounting member 6134 (FIG. 132) that holds or otherwiseconnects to the second circuit board 6124. For example, the firstmounting member 6134 may be fastened, glued, soldered, welded, snap-fit,or otherwise installed on the second circuit board 6124. For example,FIG. 135 shows an example first mounting member 6134 being fastened(e.g., via screws) to a top of the second board 6124. A rail 6135 (FIG.132) extends outwardly from the first mounting members 6134. In someimplementations, the rail 6135 is axially fixed relative to the firstmounting member 6134. In one implementation, the rail 6135 is unitarywith the first mounting member 6134.

The connection assembly 6130 also includes at least a second mountingmember 6136 (FIG. 133) that is connected to the first circuit board6122. In the example shown in FIG. 135, the second mounting member 6136is fastened to the first circuit board 6122 (e.g., via screws). In otherimplementations, however, the second mounting member 6136 may be glued,soldered, welded, snap-fit, or otherwise installed on the first circuitboard 6136. For example, FIG. 135 shows an example second mountingmember 6136 being fastened to a top of the first board 6122. In someimplementations, the rails 6135 slide through an opening 6137 defined inthe second mounting members 6136 to move the first mounting member 6134toward and away from the second mounting member 6136. Moving the firstmounting member 6134 toward and away from the second mounting member6136 moves the second circuit board 6124 toward and away from the firstcircuit board 6122.

In some implementations, the connection assembly 6130 includes only asingle first mounting member 6134, a single rail 6135, and a singlesecond mounting member 6136. In other implementations, however, theconnection assembly 6130 can include two or more sets of mountingmembers 6134, 6136, and rails 6135. For example, the connection assembly6130 shown in FIGS. 131-135 includes two spaced first mounting members6134, each holding one rail 6135. The connection assembly 6130 of FIGS.131-135 also includes two spaced second mounting members 6136 configuredto slideably receive the rails 6135.

One example first mounting member 6134 is shown in FIG. 132. The firstmounting member 6134 is configured to secure to the second circuit board6124. Certain types of first mounting members 6134 include rectangularbases that are configured to be installed on the second circuit board6124. Certain types of first mounting members 6134 also include curvedtops. In the example shown, the curved top of the first mounting member6134 defines axial ribs. In other implementations, however, the firstmounting member 6134 may include a body defining a different shape(e.g., a rectangle, a triangle, etc.).

One example rail 6135 is shown in FIG. 132. In the example shown, eachrail 6135 has a circular transverse cross-section. In otherimplementations, however, the rails 6135 may have differentcross-sectional shapes (e.g., square, rectangle, oval, trapezoid, etc.)that complement the cross-sectional shapes of channels 6137 of thesecond mounting members 6136 (FIG. 133). Each of the rails 6135 isconfigured to receive a fastener 6138 (FIG. 131) that secures the rail6135 to the second mounting member 6136 to inhibit the rail 6135 fromsliding completely through the second mounting member 6136.

One example second mounting member 6136 is shown in FIG. 133. The secondmounting member 6136 is configured to secure to the first circuit board6122 (e.g., see FIGS. 134-135). The second mounting member 6136 definesa channel 6137 through which a rail 6135 may extend. Certain types ofsecond mounting members 6136 define a stepped profile on one side. Inother implementations, however, the second mounting members 6136 maydefine any suitable shape.

The connection assembly 6130 also includes a cable 6131 that connects tothe first circuit board 6122 at a first plug 6132 and that connects tothe second circuit board 6124 at a second plug 6133 (see FIG. 131). Thecable 6131 is generally flexible and is sufficiently long to enable thesecond printed circuit board 6124 to move relative to the first printedcircuit board 6122 without disconnecting from the first printed circuitboard 6122. For example, when the second printed circuit board 6124 isin the retracted position (e.g., as shown in FIG. 134), the cable 6131forms a half loop at a location between the first and second plugs 6132,6133. When the second printed circuit board 6124 is in the extendedposition (e.g., as shown in FIG. 131), the cable 6131 straightens out toextend over the distance between the printed circuit boards 6122, 6124.

In certain implementations, the connection assembly 6130 also includes aflange 6139 around which the cable 6131 may fold to manage the bendingof the cable 6131 during extension and retraction of the circuit boardarrangement 6120. For example, the flange 6139 may include an elongated,planar body extending generally parallel with the first circuit board6122. In the example shown, the free end of the elongated flange 6139 isbent, folded, or curved to inhibit damage to the cable 6131. In suchimplementations, the cable 6131 may form the half-loop around the distalend of the flange 6139 when the circuit board arrangement 6120 is in theretracted position (see FIG. 91).

For example, when the blade 6100 is being inserted into the chassis 3010and the second circuit board 6124 has not yet been connected to thebackplane 3040, the first mounting members 6134 abut the second mountingmembers 6136 and a majority of each rail 6135 protrudes forwardly of thesecond mounting members 6136 (see FIG. 91). The first and second plugs6132, 6133 of the cable 6131 are positioned adjacent each other with thefirst plug 6132 being positioned below the elongated flange 6139. Thecable 6131 wraps around the distal end of the flange 6139 and extendssubstantially along the length of both major sides of the elongatedflange 6139.

Moving the blade 6100 out of the chassis 3010 to the first extendedposition moves the second mounting members 6136 forwardly relative tothe backplane 3040. The backplane 3040 retains the connector end 6125 ofthe second printed circuit board 6124 with sufficient force to retainthe connection to the second printed circuit board 6124. Accordingly,the second mounting members 6136 slide forwardly along the rails 6135.In some implementations, the second mounting members 6136 slide alongthe rails 6135 until the second mounting members 6136 abut the ends ofthe rails 6135. In the example shown in FIG. 131, the second mountingmembers 6136 abut screw heads on the ends of the rails 6135.

Accordingly, when a user chooses to pull one of the blades 6100forwardly relative to the chassis housing 3010 (e.g., to access acommunications coupler 6150), the first cable plug 6132 of thecorresponding cable 6131 moves with the blade 6100. The second cableplug 6133, however, remains at a fixed position relative to thebackplane 3040. For example, if a user wants to add, remove, or replacean outgoing media segment 3200 on a blade 6100, then the user can slidethe blade 6100 to the first extended position to access the desiredsegment or coupler port without disconnecting the storage devices of theremaining physical media segments 6200 mounted to the blade 6100 fromthe data management network.

In some implementations, moving the blades 6100 further out of thechassis 3010 (e.g., to the second extended position) disconnects theblades 6100 from the backplane 3040 and, hence, from the data network.As discussed above, moving the blade 6100 to the second extendedposition may facilitate access the rear ports of the front couplers 6151through an open top of the blade 6100. In other implementations, themoving the blade 6100 to the second extended position enables a user toaccess (e.g., add, remove, or replace) the blade processor 6140. Inother implementations, however, the user can access the processor 6140when the blade 6100 is in the first extended position.

In FIGS. 136-142, the example blade 6100 includes a second exampleconnection system 6130′ that connects the processor 6140 to thebackplane 3040 of the chassis 3010. The second connection assembly 6130′includes at least a first mounting member 6134′ that holds or otherwiseconnects to the second circuit board 6124. The first mounting member6134′ mounts the second circuit board 6124 on rails 6135′ that areconnected to the first circuit board 6122 via second mounting members6136′. In some implementations, the rails 6135′ slide through the secondmounting members 6136′ to move the second printed circuit board 6124relative to the first printed circuit board 6122. In otherimplementations, the first mounting members 6134′ move over the rails6135′ to move the second printed circuit board 6124 relative to thefirst printed circuit board 6122.

One example first mounting member 6134′ is shown in FIG. 140. The firstmounting member 6134′ is configured to mount on rails 6135′. In theexample shown, the first mounting member 6134′ includes a generallyT-shaped body that defines an open-ended slot through which a rail 6135′can extend. In other implementations, however, the first mounting member6134′ may include a body defining a different shape (e.g., a rectangle,a triangle, etc.). In other implementations, the first mounting member6134′ may define through-opening instead of a slot. In someimplementations, one first mounting member 6134′ is installed at a firstside of the second printed circuit board 6124 and another first mountingmember 6134′ is installed at a second side of the second printed circuitboard 6124. In certain implementations, the second printed circuit board6124 is held between two first mounting members 6134′. In otherimplementations, the first mounting members 6134′ are mounted on top ofthe second printed circuit board 6124 (e.g., see FIG. 139).

The rails 6135′ are connected to the first printed circuit board 6122 bysecond mounting members 6136′. One example second mounting member 6136is shown in FIG. 141. The second mounting member 6136′ defines a channel6137′ through which one of the rails 6135′ may extend. One example rail6135′ is shown in FIG. 142. In the example shown, each rail 6135′ has acircular transverse cross-section. In other implementations, however,the rails 6135′ may have different cross-sectional shapes (e.g., square,rectangle, oval, trapezoid, etc.) that complement the cross-sectionalshapes of channels 6137′ of the second mounting members 6136′. Each ofthe rails 6135′ includes a stop 6138′ at one end to inhibit the rail6135′ from sliding completely through the first mounting member 6134′.

The connection assembly 6130′ also includes the cable 6131 that connectsto the first circuit board 6122 at the first plug 6132 (FIG. 138) andthat connects to the second circuit board 6124 at the second plug 6133(FIGS. 131 and 138). The cable 6131 is generally flexible and issufficiently long to enable the second printed circuit board 6124 tomove relative to the first printed circuit board 6122 withoutdisconnecting from the first printed circuit board 6122. For example,when the second printed circuit board 6124 is in the retracted position(e.g., as shown in FIG. 137), the cable 6131 can form a half loop at alocation between the first and second connectors 6132, 6133. When thesecond printed circuit board 6124 is in the extended position (e.g., asshown in FIG. 138), the cable 6131 substantially straightens out toextend over the distance between the printed circuit boards 6122, 6124.

In certain implementations, the second connection assembly 6130′ alsoincludes the flange 6139 around which the cable 6131 may fold to managethe bending of the cable 6131 during extension and retraction of thecircuit board arrangement 6120. For example, the flange 6139 may includean elongated, planar body extending generally parallel with the firstcircuit board 6122. In the example shown, the free end of the elongatedflange 6139 is bent, folded, or curved to inhibit damage to the cable6131. In such implementations, the cable 6131 may form the half-looparound the distal end of the flange 6139 when the circuit boardarrangement 6120 is in the retracted position (see FIG. 136).

For example, in the example shown in FIG. 137, the blade 6100 is beinginserted into the chassis 3010 and the second circuit board 6124 has notyet been connected to the backplane 3040. The first mounting members6134 abut the second mounting members 6136′ and a majority of each rail6135′ protrudes forwardly of the second mounting members 6136′. Thefirst and second plugs 6132, 6133 are positioned adjacent each otherwith the first plug 6132 positioned below the elongated flange 6139. Thecable 6131 wraps around the distal end of the flange 6139 and extendssubstantially along the length of both major sides of the elongatedflange 6139.

Moving the blade 6100 out of the chassis 3010 to the first extendedposition moves the second mounting members 6136′ forwardly relative tothe backplane 3040. The backplane 3040 retains the connector end 6125 ofthe second printed circuit board 6124 with sufficient force to retainthe connection to the second printed circuit board 6124. Accordingly,the second mounting members 6136′ slide forwardly along the rails 6135′.In some implementations, the second mounting members 6136′ slide alongthe rails 6135′ until the second mounting members 6136′ abut the ends ofthe rails 6135′. In the example shown in FIG. 139, the second mountingmembers 6136′ abut screw heads on the ends of the rails 6135′.

Accordingly, when a user chooses to pull one of the blades 6100forwardly relative to the chassis housing 3010 (e.g., to access acommunications couplers 6151), the first cable plug 6132 of thecorresponding cable 6131 moves with the blade 6100. The second cableplug 6133, however, remains at a fixed position relative to thebackplane 3040. For example, if a user wants to add, remove, or replacean outgoing media segment 3200 on a blade 6100, then the user can slidethe blade 6100 to the first extended position to access the desiredsegment or coupler port without disconnecting the storage devices of theremaining physical media segments 3200 mounted to the blade 6100 fromthe data management network.

In some implementations, moving the blades 6100 further out of thechassis 3010 (e.g., to the second extended position) disconnects theblades 6100 from the backplane 3040 and, hence, from the data network.As discussed above, moving the blade 6100 to the second extendedposition may facilitate access the rear ports of the front couplers 6151through an open top of the blade 6100. In other implementations, themoving the blade 6100 to the second extended position enables a user toaccess (e.g., add, remove, or replace) the blade processor 6140. Inother implementations, however, the user can access the processor 6140when the blade 6100 is in the first extended position.

FIGS. 143-150 illustrate one example bladed panel system 7000 includinga “passive” chassis 7010 and a plurality of “passive” blades 7100. Inother implementations, however, one or more smart blades 6100 may bemounted to the passive chassis 7010. The chassis 7010 includes sidewalls 7011 interconnected by top and bottom walls 7012 to define an openfront and an open rear. A rear cover 7050 may be mounted to the chassis7010. In certain implementations, the rear cover 7050 is substantiallythe same as rear cover 3050 disclosed above. In contrast to chassis 3010above, however, the example chassis 7010 does not include a backplane.In some implementations, a panel 7040 may be mounted in place of abackplane. In other implementations, the rear of the chassis 7010 may beleft open.

One or more guides 7015 are positioned along the side walls 7011. Theblades 7100 are moveably positioned in the chassis 7010 using the guides7015. For example, the blades 7100 may be slid along the guides 7015. Incertain implementations, the guides 7015 extend between the front andrear of the chassis 7010. In the example shown, the chassis 7010includes eight guides 7015. In other implementations, however, thechassis 7010 may include greater or fewer guides (e.g., one guide, twoguides, three guides, four guides, ten guides, twelve guides, etc.).

FIG. 146 shows one example implementation of a first passive blade 7100Aincluding a coupler arrangement 7150A having one or more passivecouplers 7151. As the term is used herein, a “passive” blade 7100 is ablade that does not include PLI/PLM functionality. In someimplementations, a passive blade 7100 does not include a circuit boardarrangement. In other implementations, a passive blade 7100 may includecouplers 7151 that do not have media reading interfaces. In certainimplementations, the passive couplers 7151 are configured to receivemedia segments 3200 regardless of whether the media segment 3200includes a storage device storing physical layer information. In theexample shown, dust caps 7152 are positioned at the front ports of theblade 7100A.

In the example shown, the first passive blade 7100A includes a generallyplanar base 7110 having outer and inner extensions 7111, 7113. At leastone of the outer extensions 7111 defines a notch 7005 that enables theblade 7100A to be locked in a closed position within the chassis 7010 asdescribed above. The inner extensions 7113 define cable tie locations7039 at which media segments may be secured to the base 7110. One ormore latching tabs 7170, 7176 may be positioned on the base 7110 toenable the blade 7100A to be locked into one or more positions relativeto the chassis 7010. In other implementations, other types of latchingsystems may be used with blade 7100A.

A handle 7108 extends forwardly of the base 7110 to facilitate movementof the blade 7100A relative to the chassis 7010. A frame 7115 ispositioned at the front of the first passive blade 7100A. The frame 7115is configured to secure one or more passive couplers 7151 to the base7110. In some implementations, the couplers 7151 are configured toreceive both incoming media segments 3210 and outgoing media segments3220. In other implementations, the couplers 7151 receive only outgoingmedia segments 3220 and couplers positioned at the rear of the base 7110receive the incoming media segments 3210. Retention fingers 7160 extendforwardly of the frame 7115. In certain implementations, the retentionfingers 7160 are substantially the same as retention fingers 3160described above.

FIGS. 147 and 148 show one example implementation of the frame 7115. Theexample frame 7115 includes parallel top and bottom members 7090, 7091,respectively, connected by a front panel 7192. The front panel 7192defines one or more openings 7193 configured to receive the couplerarrangement 7150 of the blade 7100A. In some implementations, anintermediate section 7198 of the frame 7115 has a reduced heightcompared to outer sections of the frame 7115. In some implementations,the reduced height section 7198 also defines openings 7196 configured toreceive couplers 7151. In other implementations, the reduced heightsection 7198 defines a blank flange extending between the outer sectionsof the frame 7115.

In some implementations, each opening 7193 is sized to receive a singlecoupler 7151 and the openings 7193 are separated by dividing flanges7194. For example, in one implementation, each opening 7193 may be sizedto receive a simplex coupler 7151. In another implementation, eachopening 7193 is sized to receive a duplex coupler 7151. In yet anotherimplementation, each opening 7193 is sized to receive a quadruplexcoupler 7151. In still other implementations, each opening 7193 may besized to receive various other sized couplers. In some implementations,the openings 7193 are separated into two or more groups by dividingsections 7195 (FIG. 148). The dividing sections 7195 are thicker thandividing flanges 7194.

In some implementations, the frame 7115 is configured to receive one ormore couplers 7151 configured to receive media segments terminated withSC-type connectors (see FIG. 146). In other implementations, the frame7115 is configured to receive one or more couplers 7151 configured toreceive media segments terminated with LC-type connectors (see couplers7157 of the second example passive blade 7100B of FIG. 149). In stillother implementations, the frame 7115 may be configured to receive mediasegments terminated with various other types of connectors (e.g.,ST-type connectors, FC-type connectors, MPO-type connectors).

For example, FIG. 150 shows a third example passive blade 7100Cincluding a base 7110, latching tabs 7170, 7176, and retention fingers7160. A frame 7115′ is positioned at the front of the base 7110 tosecure a plurality of couplers 7153 to the blade 7100C. In the exampleshown, the couplers 7153 are configured to receive MPO-type connectors.In other implementations, however, the frame 7115′ may be configured toreceive other types of couplers. The frame 7115′ includes a reducedheight section 7116 that is not configured to hold any couplers. Rather,the reduced height section 7116 of the frame 7115′ includes a generallyplanar face that extends between groups of front couplers 7153. In theexample shown, dust caps 7154 are received at the front ports of thecouplers 7153.

As shown in FIGS. 143 and 144, a single chassis 7010 may receive one ormore types of blades 7100. For example, the chassis 7010 shown in FIG.144 has received a third example passive blade 7100C at each of the toptwo guides 7015, a second example passive blade 7100B at each of thethree intermediate guides 7015, and a first example passive blade 7100Aat each of the three bottom guides 7015. In other implementations, theguides 7100 may be arranged in the chassis 7010 in a differentconfiguration.

In still other implementations, any of the passive blades 7100A, 7100B,7100C may be positioned in a chassis that includes a backplane (e.g.,chassis 3010 disclosed above). For example, in some implementations, therear of each of the passive chasses 7100A, 7100B, 7100C terminatesbefore the backplane 3040 when the chassis 7100A, 7100B, 7100C ismounted to a smart chassis 3010 in a closed position. In certainimplementations, the reduced height section 7198, 7116 of the frames7115, 7115′ of the passive chasses 7100A, 7100B, 7100C accommodate astatus board (e.g., status board 3070 of FIG. 45) when received at a topof a smart chassis 3010. Further, the reduced height sections 7198, 7116of the frames 7115, 7115′ facilitate gripping the handle 7108 whenoutgoing media segments 3220 are routed to the front of the blades7100A, 7100B, 7100C (see FIG. 144).

To enhance clarity of the application, the following disclosure providesan example walk-through of routing the incoming and outgoing mediasegments 3200 for an example blade. One or more chasses (e.g., chasses1010, 2010, 3010, 5010, and 7010) are provided, for example, on anequipment rack (see rack 4400 of FIGS. 80-82). One or more blades (e.g.,blades 1100, 2100, 3100, 6100, and 7100) are installed in each chassis.In this walk-through, a smart blades, such as blade 3100, is beingmounted to a smart chassis, such as chassis 3010 having backplane 3040.A status board 3070 also may be installed at the chassis 3010 andconnected to the backplane 3040.

The blade 3100 is slid rearwardly along guides 3015 from the front ofthe chassis 3010. A circuit board arrangement 3120 of the blade 3100 isconnected to a backplane 3040 of the chassis 3010 by sliding the blade3100 rearwardly into the chassis 3010 along the guides 3015. Forexample, a second circuit board 3124 on each blade 3100 may be connectedto the backplane 3040 (e.g., via a card-edge connection, via aconnector, etc.). The blade processor 3140 on the smart blade 3100 alsois connected to the backplane 3040 via the circuit board arrangement3120.

Incoming cables 3210 may be connected to the rear ports of each blade3100 after the blade 3100 has been inserted into the chassis 3010. Forexample, a technician may plug connectorized ends 3212 of the incomingcables 3210 into the rear ports of the blade 3100. The technician alsomay secure the incoming cables 3210 to the blade 3100, the chassis 3010,and/or the frame. For example, the technician may routes the incomingcables 3210 to a cable clamp 3030, fanout arrangement 3035, or othersecurement structure at the chassis 3010 before securing the incomingcables 3210 to the blades 3100. The technician also may secure (e.g.,using a cable tie 3039) the incoming cables 3210 to the tabs on theintermediate flanges at the rear of the blades to provide slack lengthof the incoming cables 3210 between the chassis 3010 and the blade 3100.

The technician routes the connectorized ends 3212 of the incoming cables3210 to the rear ports of the blade 3100. In some implementations, thetechnician plugs the connectorized ends 3212 of the incoming cables 3210into ports 3195 (FIG. 78) defined by couplers at the rear of the blade3100. In such implementations, the technician accesses the rear ports3195 from the rear of the chassis 3010. In particular, the techniciancan unplug a dust plug 3158 (FIG. 79) from one of the rear ports 3195 ofthe rear couplers and insert one of the connectorized ends 3212 into therear port 3195 from the rear of the chassis 3010.

In other implementations, the technician feeds connectorized ends 3212of the incoming cables 3210 from the rear of the chassis 3010, over thebase of the respective blade, toward the front couplers. The technicianmay subsequently access the rear ports of the front couplers through anopen top of the blade from the front of the chassis 3010. For example,the technician may access the front couplers when the blade 3100 is in afirst or second extended position. In particular, the technician canunplug a dust plug from one of the rear ports of the front couplers andinsert each of the connectorized ends 3212 of the incoming mediasegments 3210 into one of the rear ports from the front of the chassis3010.

Outgoing cables 3220 may be installed at the front ports of the blades3100. If the blade is a smart blade, then the outgoing cables 3220 maybe installed at the front ports without disconnecting the blade 3100from the backplane 3040. For example, the technician may plug theconnectors 3222 of the outgoing cables 3220 into the front ports of thefront couplers when the blade 3100 is in the closed or first extendedposition. In other implementations, however, the connectors 3222 of theoutgoing fibers 3220 may be plugged into the front coupler ports whilethe blade 3100 is in any desired position. The technician also routesthe fibers 3220 through the retention fingers 3160 at the front of theblade 3100.

The above specification, examples and data provide a completedescription of the manufacture and use of the composition of theinvention. Since many embodiments of the invention can be made withoutdeparting from the spirit and scope of the invention, the inventionresides in the claims hereinafter appended.

1. A bladed panel system comprising: a chassis defining an interioraccessible through an open front and accessible through an open rear,the chassis having opposite first and second sidewalls extending betweenthe open front and the open rear, the sidewalls including channelmembers; a blade extending between opposite first and second sides thatengage the channel members of the chassis, the blade being slidablewithin the channel members along a front-to-rear axis that extendsbetween the open front and the open rear of the chassis to insert theblade into and to remove the blade from the interior of the chassis, theblade being insertable into and removable from the interior of thechassis through the open front and through the open rear at a discretionof a user, the blade including a base that carries a plurality ofoptical adapters, the base of the blade being slidable relative to thechassis along the front-to-rear axis between at least first and seconddiscrete positions, the second discrete position being located forwardlyof the first discrete position relative to the chassis, the base of theblade being disposed within the interior of the chassis when in thefirst position, the optical adapters defining front ports facing theopen front of the chassis when the blade is disposed in the firstposition; and a management arrangement disposed at the open rear of thechassis, the management arrangement including a bottom wall extendingrearwardly from the open rear and management sidewalls extendingrearwardly upwardly from the bottom wall, the management arrangementdefining side ports that face transverse to the front-to-rear axis. 2.The bladed panel system of claim 1, further comprising a retentionarrangement including a first retention portion disposed at the firstsidewall of the chassis and a second retention portion carried by thebase of the blade, wherein interaction between the first retentionportion and the second retention portion retains the blade at the firstdiscrete position.
 3. The bladed panel system of claim 2, wherein thefirst retention portion is a forward stop member and the secondretention portion is an engagement member carried by the blade.
 4. Thebladed panel system of claim 3, wherein the forward stop member includesa ramped structure disposed at an inner surface of the first sidewalland the engagement member includes a tab extending laterally outwardlyfrom the blade.
 5. The bladed panel system of claim 2, wherein theretention arrangement also includes a third retention portion disposedat the first sidewall of the chassis, wherein interaction between thesecond retention portion and the third retention portion retains theblade at the second discrete position.
 6. The bladed panel system ofclaim 5, wherein the third retention portion is a rearward stop memberand the second retention portion is an engagement member carried by theblade.
 7. The bladed panel system of claim 6, wherein the rearward stopmember includes a ramped structure disposed at an inner surface of thefirst sidewall and the engagement member includes a tab extendinglaterally outwardly from the blade.
 8. The bladed panel system of claim1, wherein the optical adapters are configured to optically couple firstfibers received at the front ports to second fibers extending throughthe side ports of the management arrangement.
 9. The bladed panel systemof claim 1, wherein the bottom wall of the management arrangement alignswith a bottom wall of the chassis.
 10. The bladed panel system of claim1, wherein the management sidewalls of the management arrangement alignwith the first and second sidewalls of the chassis.
 11. The bladed panelsystem of claim 1, wherein the first sidewall includes a forward stopmember disposed at the open front and a rearward stop member disposed atthe open rear, the forward stop member preventing unintentional slidingof the blade through the open front of the chassis, the rearward stopmember preventing unintentional sliding of the blade through the openrear of the chassis.
 12. The bladed panel system of claim 1, wherein thechassis is sized to fit a plurality of blades.
 13. The bladed panelsystem of claim 12, further comprising a plurality of blades mountableto the chassis to enable sliding of the blades along the front-to-rearaxis.
 14. The bladed panel system of claim 13, wherein the firstsidewall includes a plurality of forward stop members disposed at theopen front and a plurality of rearward stop members disposed at the openrear, each of the rearward stop members aligned with one of the forwardstop members, each forward stop member preventing unintentional slidingof a respective one of the blades through the open front of the chassis,each rearward stop member preventing unintentional sliding of acorresponding one of the blades through the open rear of the chassis.15. The bladed panel system of claim 1, further comprising a pluralityof retention fingers carried by and extending forwardly from the blade.16. The bladed panel system of claim 1, wherein the channel members ofthe first sidewall each include mounting pegs that fit into aperturesdefined in the first sidewall of the chassis.
 17. The bladed panelsystem of claim 1, wherein the side ports of the management arrangementinclude seals.
 18. The bladed panel system of claim 17, wherein the sideports of the management arrangement include a first port and a secondport at each management sidewall, the first port being located above thesecond port.
 19. The bladed panel system of claim 1, wherein the sideports of the management arrangement include a first port and a secondport at each management sidewall, the first port being located above thesecond port.
 20. The bladed panel system of claim 1, wherein the bottomwall of the management arrangement includes a rear lip.